From: Thomas Rast <trast@student.ethz.ch>
To: <pascal@obry.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Nicolas Pitre <nico@fluxnic.net>, E R <pc88mxer@gmail.com>,
<git@vger.kernel.org>, Jeff King <peff@peff.net>
Subject: Re: keeping track of where a patch begins
Date: Fri, 30 Oct 2009 09:37:18 +0100 [thread overview]
Message-ID: <200910300937.22949.trast@student.ethz.ch> (raw)
In-Reply-To: <4AEA94EB.8080304@obry.net>
Pascal Obry wrote:
>
> Le 22/10/2009 10:27, Thomas Rast a écrit :
> > I think this not only changes the model of branches, but also commits,
> > to some extent. Currently, commit have no intrinsic branch
> > membership
[...]
> To me there is case where it is important to know which are the commits
> done on a topic branch for example. When working on multiple topic it is
> difficult to remember which commits have been done on this specific
> branch. This is needed to rebase onto:
>
> $ git rebase --onto somebranch <topic_base> <topic_head>
>
> A common idiom, but one as to think hard (& right) to properly get the
> topic_base today.
But how frequently do your topics start on other topics? Otherwise
they will start on an integration or maint branch, and in the git.git
model where each integration branch is contained in the next "less
stable" one, that means you can just specify 'pu' or equivalent.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2009-10-30 8:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 14:45 keeping track of where a patch begins E R
2009-10-21 18:14 ` Nicolas Pitre
2009-10-21 20:03 ` Junio C Hamano
2009-10-21 20:50 ` Nicolas Pitre
2009-10-22 8:27 ` Thomas Rast
2009-10-30 7:25 ` Pascal Obry
2009-10-30 8:37 ` Thomas Rast [this message]
2009-10-26 14:30 ` Jeff King
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=200910300937.22949.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nico@fluxnic.net \
--cc=pascal@obry.net \
--cc=pc88mxer@gmail.com \
--cc=peff@peff.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).