From: Theodore Tso <tytso@mit.edu>
To: Jeff King <peff@peff.net>
Cc: Wincent Colaiuta <win@wincent.com>,
John Tapsell <johnflux@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: git rebase -i
Date: Thu, 19 Feb 2009 09:57:15 -0500 [thread overview]
Message-ID: <20090219145715.GC14810@mini-me.lan> (raw)
In-Reply-To: <20090219102053.GA17417@coredump.intra.peff.net>
On Thu, Feb 19, 2009 at 05:20:53AM -0500, Jeff King wrote:
> > Yes, I do the same. But notice that you did "git rebase -i --
> > >>>origin<<<---". Seems to me you are definitely _thinking_ in terms of
> > your topic _branch_ and not in terms of "the last few commits".
>
> Perhaps. I think of it as "the set of commits not yet published"
> (since I publish only by sending patches to Junio, and he is my origin)
> and nothing to do with the topic branch itself.
Indeed, I bet most people who use this workflow think of git rebase -i
origin or "git rebase -i HEAD^^^^" (where I normally figure out how
many commits I need to go back and type the right number of carets) as
a magic command that does what we want, without necessarily thinking
about why it works the way that it does.
I can guarantee that most of the time I don't think "hmm, so I'm going
to be rebasing my topic branch onto origin so I can make some
changes." Nope, it's, "I'm going to futz with the commits to get them
just right".
- Ted
next prev parent reply other threads:[~2009-02-19 15:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 9:21 git rebase -i John Tapsell
2009-02-19 9:36 ` Wincent Colaiuta
2009-02-19 9:55 ` John Tapsell
2009-02-19 9:59 ` Wincent Colaiuta
2009-02-19 10:11 ` Jeff King
2009-02-19 10:15 ` Wincent Colaiuta
2009-02-19 10:20 ` Jeff King
2009-02-19 14:57 ` Theodore Tso [this message]
2009-02-19 9:50 ` Teemu Likonen
2009-02-19 9:52 ` John Tapsell
2009-02-19 14:02 ` Sitaram Chamarty
2009-02-19 14:24 ` John Tapsell
2009-02-23 0:32 ` Stephan Beyer
2009-02-19 10:00 ` Pieter de Bie
2009-02-19 10:09 ` Junio C Hamano
2009-02-19 16:12 ` Marc Branchaud
2009-02-19 17:53 ` Nazri Ramliy
2009-02-19 10:01 ` Thomas Rast
2009-02-19 10:03 ` John Tapsell
2009-02-19 10:07 ` Jeff King
2009-02-19 20:55 ` Jay Soffian
2009-02-19 21:04 ` Johannes Schindelin
2009-02-19 21:07 ` Jay Soffian
2009-02-19 23:53 ` Giuseppe Bilotta
2009-02-20 0:07 ` Johannes Schindelin
2009-02-20 0:11 ` Junio C Hamano
2009-02-20 0:26 ` Jay Soffian
2009-02-20 11:02 ` Michael J Gruber
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=20090219145715.GC14810@mini-me.lan \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=johnflux@gmail.com \
--cc=peff@peff.net \
--cc=win@wincent.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.