From: Shawn Pearce <spearce@spearce.org>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH 1/2] Allow users to require source branch on git-checkout -b.
Date: Fri, 8 Dec 2006 01:19:16 -0500 [thread overview]
Message-ID: <20061208061916.GF13999@spearce.org> (raw)
In-Reply-To: <20061208060850.GE5939@fieldses.org>
"J. Bruce Fields" <bfields@fieldses.org> wrote:
> On Fri, Dec 08, 2006 at 12:59:38AM -0500, Shawn Pearce wrote:
> > Its in the prompt for all of these users; I forced it in as part of
> > the system's /etc/profile.d. They just forget that they should think
> > about where they should start their branch from before they make it.
>
> Maybe they don't really want to use topic branches at all? Could they
> get away with just committing everything to master? Seems like kind of
> a shame, though. Hm.
Good idea. But...
No, because they are working on at least two different unrelated
changes at once, and we aren't sure which will graduate into the
testing environment first. If the unrelated changes are intermingled
on the same branch then moving one moves both; and often at least
one of those unrelated changes isn't functioning right and could
cause headaches for the testing team.
--
next prev parent reply other threads:[~2006-12-08 6:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 10:01 [PATCH 1/2] Allow users to require source branch on git-checkout -b Shawn O. Pearce
2006-12-07 19:48 ` Junio C Hamano
2006-12-07 19:57 ` Shawn Pearce
2006-12-07 21:23 ` Junio C Hamano
2006-12-07 21:40 ` J. Bruce Fields
2006-12-07 21:59 ` Shawn Pearce
2006-12-08 4:45 ` J. Bruce Fields
2006-12-08 5:59 ` Shawn Pearce
2006-12-08 6:08 ` J. Bruce Fields
2006-12-08 6:19 ` Shawn Pearce [this message]
2006-12-08 6:31 ` Junio C Hamano
2006-12-08 15:39 ` J. Bruce Fields
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=20061208061916.GF13999@spearce.org \
--to=spearce@spearce.org \
--cc=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).