On Wed, Jun 18, 2008 at 03:52:40PM -0700, Chris Kuethe wrote:
> On Wed, Jun 18, 2008 at 3:10 PM, Darrin Chandler
> <[EMAIL PROTECTED]> wrote:
> > You'll notice those commits are preceeded by other commits. Often this
> > is the case when a device is added to a file and committed, then stuff
> > is autogenerated. Comitting the autogenerated stuff separately makes it
> > easier to see the real change, and the real log message is with the
> > original commit.
> 
> Not just easier to see but more accurate and useful.
> 
> Let's say I add a new usb device to usbdevs r1.358, generate all the
> headers and commit. usbdevs*.h will say they were generated from
> 1.358, but if a user tries to check out 1.358, they won't be able to
> rebuild usbdevs*.h and get the same contents. By committing the source
> first, and then the regenerated files, you ensure that you get
> consistency between all the files and everyone gets the same, correct
> output when they check out and build.

I hadn't considered that. Thanks!

-- 
Darrin Chandler            |  Phoenix BSD User Group  |  MetaBUG
[EMAIL PROTECTED]   |  http://phxbug.org/      |  http://metabug.org/
http://www.stilyagin.com/  |  Daemons in the Desert   |  Global BUG Federation

Reply via email to