From: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>,
Francis Moreau <francis.moro@gmail.com>,
Michael J Gruber <git@drmicha.warpmail.net>,
git@vger.kernel.org
Subject: Re: git-rebase skips automatically no more needed commits
Date: Thu, 15 Sep 2011 21:27:08 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1109151956040.12564@debian> (raw)
In-Reply-To: <7vwrdaqxpk.fsf@alter.siamese.dyndns.org>
Hi,
On Wed, 14 Sep 2011, Junio C Hamano wrote:
> What I said is "all 'am' need to use from its input while rebasing is the
> commit object name"; that is very different from "we have only commit
> object name so we must use cherry-pick" or "because we have commit object
> name, we can afford to use cherry-pick".
Right. I didn't mean to suggest that we should use cherry-pick.
> Look for $rebasing in git-am.sh and notice that:
Thanks! I had no idea about these "tricks" in git-am.sh. Now I
understand much better what you meant. So we are currently getting the
metainfo from the commit rather than from the mailbox. With your
patch, we would also get the patch body from the commit. The only
thing remaining after that is the commit log message, correct?
Once all that git-am reads from the mailbox while in $rebasing mode is
the commit name, it would be as small change to teach it to read a
list of commit names instead. Is this what you meant or did you really
mean for format-patch to generate output without patch body? At this
point the name 'am' becomes quite misleading, but maybe that's not
worth worrying about.
Thanks,
Martin
next prev parent reply other threads:[~2011-09-16 1:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 16:08 git-rebase skips automatically no more needed commits Francis Moreau
2011-09-06 17:09 ` Junio C Hamano
2011-09-06 19:28 ` Francis Moreau
2011-09-07 13:19 ` Michael J Gruber
[not found] ` <CAC9WiBi_bkLNJZckq2fr3eb6ie+KVfauE_PyA3GcaW5Ga-isFw@mail.gmail.com>
2011-09-07 16:29 ` Junio C Hamano
2011-09-08 7:10 ` Francis Moreau
2011-09-08 13:14 ` Martin von Zweigbergk
[not found] ` <CAC9WiBiMYUfaPtrXyW=W7qaZnJqLeFO-B3od7X4u8wUrb8hfUA@mail.gmail.com>
2011-09-09 2:23 ` Martin von Zweigbergk
2011-09-09 6:43 ` Francis Moreau
2011-09-09 13:06 ` Martin von Zweigbergk
2011-09-09 13:25 ` Francis Moreau
2011-09-15 2:19 ` Martin von Zweigbergk
2011-09-15 3:41 ` Junio C Hamano
2011-09-16 1:27 ` Martin von Zweigbergk [this message]
2011-09-20 20:45 ` Martin von Zweigbergk
2011-09-24 9:12 ` Ramkumar Ramachandra
2011-09-25 3:25 ` Martin von Zweigbergk
2011-09-26 9:10 ` Thomas Rast
2011-09-28 14:49 ` Martin von Zweigbergk
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=alpine.DEB.2.00.1109151956040.12564@debian \
--to=martin.von.zweigbergk@gmail.com \
--cc=francis.moro@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox