Boost logo

Boost :

From: troy d straszheim (troy_at_[hidden])
Date: 2007-06-06 12:33:16


in the previous thread,
On Wed, Jun 06, 2007 at 08:49:14AM -0400, David Abrahams wrote:
>
[snip]
>
> It depends where you're committing things. One of the best reasons
> for branching in a traditional version control setup is to give
> authors a place to check in their partially-finished (i.e. "broken")
> work. That _improves_ results in numerous ways. Obviously, there has
> to be some kind of check in the system for bad commits, but only those
> that a library author declares to be "good," and thus, ready for
> release.

Since we're talking about devel vs. stable and what the meaning of
'trunk' really is, I found Linus Torvald's google tech talk on git
(which is source control for the linux kernel) to be *very*
interesting (fairly entertaining as well).

  http://www.youtube.com/watch?v=4XpnKHJAok8

He places a very high value on the ability to

  * branch at any time
  * merge easily
  * commit/branch/merge locally (not in the 'central' repository)

Interesting the emphasis on git's being distributed... there is no
'central repository'.

-t


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk