DragonFly submit List (threaded) for 2008-03
DragonFly BSD
DragonFly submit List (threaded) for 2008-03
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: [patch] clear direction flag for signal handlers


From: Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>
Date: Sat, 15 Mar 2008 11:16:38 -0700 (PDT)

:On Friday 14 March 2008, Matthew Dillon wrote:
:[...]
:>     It all looks good, definitely commit it and maybe even MFC it to
:>     the release branch too.
:
:Committed. We don't have gcc-4.3 or icc in 1.12 so I don't think this needs
:to go in the release branch (but if it did, the correct way to do it would
:be with "cvs commit -r DragonFly_RELEASE_1_12 [files]", right? Sorry, but
:I haven't used cvs for development since the first free software distributed
:scm became available[*], so perhaps there's an extra quirk I don't remember
:about?)
:
:Aggelos
:
:[*] If you think git is weird, you should try pre-tla arch :)

    I wouldn't recommend using a cvs commit line like that, it's liable
    to create problems.

    What I suggest is you do a checkout, in a different directory, of
    the 1.12 release branch.  Do the MFC's within that checkout and commit
    normally.  Most of the time you can patch changes from HEAD into
    a checked out release by using something like this:

    cvs diff -r<rev1> -r<rev2> file | patch

    It's more steps to do it this way, but much safer and you can review
    the changes made prior to committing them.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]