Re: Git Vs. Svn for a project which *must* distribute binaries too.
- From
Theodore Tso <tytso@mit.edu>
- Date
- Jun 5, 2007, 11:19 UTC
- Message-ID
- <20070605111904.GA12755@thunk.org>
- In-Reply-To
- <20070604223003.GJ6528@ca-server1.us.oracle.com>
On Mon, Jun 04, 2007 at 03:30:03PM -0700, Joel Becker wrote:
Show 5 quoted lines
> It survives because it is well-known. Everyone expects it to > break. ocfs2 has an "ALL" branch that is everything we have working, > sort of a "test this bleeding edge" thing. It gets rebased all the > time, and everyone knows that they can't trust it to update linearly. > Other developers have similar things in their repositories.
I wonder if it would be useful to be able to be able to flag a branches as "jumping around a lot", where this flag would be downloaded from another repository when it is cloned, so that a naive user could get some kind of warning before committing a patch on top of one of these branches that is known jump around.
"This branch gets rebased all the time and is really meant for testing. If you really want to commit this changeset, please configure yourself for expert mode or use the --force."
Or maybe just a warning, ala what we do with detached heads.
- Ted