similar to: [ANNOUNCE] Samba 3.2.0pre3

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ================================= Release Notes for Samba 3.2.0rc2 June 10, 2008 ================================= This is the second release candidate of Samba 3.2.0. This is *not* intended for production environments and is designed for testing purposes only.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ================================= Release Notes for Samba 3.2.0rc2 June 10, 2008 ================================= This is the second release candidate of Samba 3.2.0. This is *not* intended for production environments and is designed for testing purposes only.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Preamble: Please help us testing this release candidate! If there are no major catastrophes, it will become the first major release of Samba 3.2.0. It might take a few hours until the files will be spread to all mirrors. ================================= Release Notes for Samba 3.2.0rc1

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Preamble: Please help us testing this release candidate! If there are no major catastrophes, it will become the first major release of Samba 3.2.0. It might take a few hours until the files will be spread to all mirrors. ================================= Release Notes for Samba 3.2.0rc1

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== "Patience is the companion of wisdom." Saint Augustine ============================================================== Release Announcements ===================== This is the first stable release of Samba 3.2.0. Please be aware that Samba is now distributed under

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== "Patience is the companion of wisdom." Saint Augustine ============================================================== Release Announcements ===================== This is the first stable release of Samba 3.2.0. Please be aware that Samba is now distributed under

In my project I have a group of foreign types (C++ classes) that I want to use, but don't want to represent as structs within LLVM. For example, for each field in each C++ class I have a setter and getter function that I'd like to use. The setters and getters are "extern C" functions to avoid problems with C++'s name mangling. After going over the documentation it

On 1 December 2011 17:15, Chris Lattner <clattner at apple.com> wrote: > > On Dec 1, 2011, at 5:09 PM, Nick Lewycky wrote: > >> I'm running LLVM under threadsanitizer >> (http://code.google.com/p/data-race-test/) to find and remove races in >> a larger program that uses LLVM as a library. One of the things that I >> found is that the TargetOptions are all

?Hello fellow developers, yesterday, I was thinking about how to implement specific config. attributes accessors in section-based nut config. files so that it's nice to use and consistent with NutConfiguration, UpsmonConfiguration and UpsdConfiguration config. classes (where it's done via Settable attributes). The GenericConfiguration class provides generic access to name/value items of

On Dec 1, 2011, at 5:09 PM, Nick Lewycky wrote: > I'm running LLVM under threadsanitizer > (http://code.google.com/p/data-race-test/) to find and remove races in > a larger program that uses LLVM as a library. One of the things that I > found is that the TargetOptions are all global; you could create a > TargetMachine targeting ARM and X86 in two threads, but they both have

I'm running LLVM under threadsanitizer (http://code.google.com/p/data-race-test/) to find and remove races in a larger program that uses LLVM as a library. One of the things that I found is that the TargetOptions are all global; you could create a TargetMachine targeting ARM and X86 in two threads, but they both have to share the same FloatABIType setting. This is silly, and I plan to fix it

Hey everyone, I am developing a package and I am wondering if there is a good practice for naming classes, builders, attributes getters and setters when dealing with object composition. I know that it is usually a good practice to give to the builder the same name as the class and, if possible, to avoid to use upper case letters. My problem is that, when I build an object containing an other

On Dec 1, 2011, at 5:23 PM, Nick Lewycky wrote: >> Instead of adding a bunch of instance variables (+ getters/setters) into TargetMachine, why not make TargetOptions be a class, and have TM contain an instance of it? > > That works too, it makes little difference to me. One reason is that > most references to these globals are inside classes that derive from > TargetMachine so I

This rule does not seem to be widely followed by Clang today. Looking at Parser and Sema, many getters (0 argument functions with names matching /^get[A-Z]/) return mutable references to long-lived objects. Looking through Decl.h, things are a little different: we rarely return references, but do frequently return pointers that provide mutable access to contained objects. On Tue, Mar 4, 2014 at

Im developing a User model for my application (newbie stuff, but I have to start somewhere). I followed the tutorial at http://sonjayatandon.com/05-2006/how-to-build-a-secured-web-application-with-ruby-on-rails/ and decided to add an email field. The problem is that the email is not being saved on the database and I end up with two email variables: @email and email. validates_presence_of

Studying the RoR 3 Tutorial book by Michael Hartl and on page 345 there''s the code inside the SessionsHelper: _________________________________________________________ module SessionsHelper def sign_in(user) cookies.permanent.signed[:remember_token] = [user.id, user.sault] self.current_user = user end end __________________________________________________________ What is the purpose

On Mar 3, 2014, at 10:29 AM, Chandler Carruth <chandlerc at google.com> wrote: > > On Mon, Mar 3, 2014 at 9:48 AM, Chris Lattner <sabre at nondot.org> wrote: >> In the best case 'get' doesn't really add any meaning, and in the worst case it is actively misleading > > It's getting the range though, just like Function::getArgumentList() returns the

Hi As we''re getting closer to a stable release of wxRuby, I''d like to get your views on the API style. There''s a survey here: http://rubyforge.org/survey/survey.php?group_id=35&survey_id=66 I''d like to know if you''d like to see two wxSugar syntax features become part of core, standard wxRuby version 2.0. These are: 1) Allow ruby-style

In the Ruby bindings, set_X and get_X are renamed to remove the get/set, so MSet::get_matches_estimated() becomes a read-only property (if I have my terminology right) of the Ruby MSet class called matches_estimated. This matches how a Ruby programmer would expect a class to be designed. I was looking through the getters and setters list. I wonder if a few entries shouldn't be there, (the

Hi Rubyists! I''m quite new to Ruby/Rails thing, so please be patient with me :) -------- (skip to next -------- if you want to quickly see the problem) I am learning by creating something like timetable application (like in school). There are days 1-5 and lessons 1-8. I have to db tables, subjects, which is the list of subjects, and subject_lessons, which is assocation of a subject to