From: Theodore Tso <tytso@mit.edu>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Olivier Galibert <galibert@pobox.com>,
Thomas Glanzmann <thomas@glanzmann.de>,
Bryan Childs <godeater@gmail.com>,
git@vger.kernel.org
Subject: Re: Git Vs. Svn for a project which *must* distribute binaries too.
Date: Tue, 5 Jun 2007 07:19:04 -0400 [thread overview]
Message-ID: <20070605111904.GA12755@thunk.org> (raw)
In-Reply-To: <20070604223003.GJ6528@ca-server1.us.oracle.com>
On Mon, Jun 04, 2007 at 03:30:03PM -0700, Joel Becker wrote:
> 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
next prev parent reply other threads:[~2007-06-05 11:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 11:48 Git Vs. Svn for a project which *must* distribute binaries too Bryan Childs
2007-06-04 11:56 ` Julian Phillips
2007-06-04 13:18 ` Theodore Tso
2007-06-04 14:58 ` Johannes Schindelin
2007-06-04 15:20 ` Linus Torvalds
2007-06-04 15:38 ` Bryan Childs
2007-06-04 16:23 ` Linus Torvalds
2007-06-04 17:57 ` Thomas Glanzmann
2007-06-04 20:45 ` Linus Torvalds
2007-06-04 21:21 ` Olivier Galibert
2007-06-04 21:33 ` Linus Torvalds
2007-06-04 22:30 ` Joel Becker
2007-06-05 11:19 ` Theodore Tso [this message]
2007-06-05 2:56 ` Johannes Schindelin
2007-06-04 22:29 ` Martin Langhoff
2007-06-04 23:48 ` Daniel Barkalow
2007-06-05 0:21 ` Linus Torvalds
2007-06-05 1:42 ` david
2007-06-05 3:58 ` Linus Torvalds
2007-06-04 23:46 ` Jakub Narebski
2007-06-06 22:34 ` Jakub Narebski
-- strict thread matches above, loose matches on Subject: below --
2007-06-07 4:36 linux
2007-06-07 7:57 ` Bryan Childs
2007-06-07 16:51 ` linux
2007-06-08 20:41 ` Jan Hudec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070605111904.GA12755@thunk.org \
--to=tytso@mit.edu \
--cc=Joel.Becker@oracle.com \
--cc=galibert@pobox.com \
--cc=git@vger.kernel.org \
--cc=godeater@gmail.com \
--cc=thomas@glanzmann.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).