From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Attempt to improve git-rebase lead-in description.
Date: Sun, 18 Feb 2007 03:21:14 +0100 [thread overview]
Message-ID: <er8d34$ssm$1@sea.gmane.org> (raw)
In-Reply-To: 20070217093150.GA25871@spearce.org
Shawn O. Pearce wrote:
> +
> +The commits that were previously saved into the temporary area are
> +then reapplied to the current branch, one by one, in order.
Which is true for git-format-patch/git-am --3way driven "git rebase",
but not for git-merge driven "git rebase --merge".
The description is certainly more user-friendly, but I'd rather it avoid
mentioning saving to temporary area.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-02-18 2:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-17 9:31 [PATCH] Attempt to improve git-rebase lead-in description Shawn O. Pearce
2007-02-18 2:21 ` Jakub Narebski [this message]
2007-02-18 6:31 ` Shawn O. Pearce
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='er8d34$ssm$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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 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.