From: Vincent van Ravesteijn <vfr@lyx.org>
To: lei yang <yanglei.fage@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [git-users] Re: how to get the formated patches from the merge id
Date: Fri, 15 Jun 2012 15:11:59 +0200 [thread overview]
Message-ID: <4FDB349F.3080507@lyx.org> (raw)
In-Reply-To: <CAHsH0E8MzMW8SEFGB_X80qH_5btnmvLWFxjQ-EBSaGbHSUz-Sg@mail.gmail.com>
Op 15-6-2012 14:56, lei yang schreef:
> On Fri, Jun 15, 2012 at 7:59 PM, Vincent van Ravesteijn<vfr@lyx.org> wrote:
>> It is still not clear what you want to accomplish.
>>
>> Your proposal: "git format-patch b724cc1..51bfd29" only gives you the
>> commits that were in the branch 51bfd29 that weren't yet in the branch
>> b724cc1. This just reflect the commits of one of the branches, but not the
>> "work done by the merge commit".
>>
>
> but,git format-patch b724cc1..51bfd29 do the same work as what you
> said "git format-patch 0e93b4b3^1..0e93b4b3^2"
Yes, that's why I said "If this is _really_ what you want, you can do ...".
> and I don't understand what you
> said "branch 51bfd29",51bfd29 is not the branch
I assumed that the merge commit, merged two branches, but I have no clue
how they were named. That's why I refer to the branch as the branch
which had 51bfd29 as the last commit before the merge.
Vincent
next prev parent reply other threads:[~2012-06-15 13:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 16:25 how to get the formated patches from the merge id lei yang
[not found] ` <CAHsH0E98t7EcvXM0zSjMGHcd5u4_Lp6B7q9KAhcE0eyo-tXnWw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-06-15 8:02 ` Thomas Ferris Nicolaisen
[not found] ` <9579793f-d72f-424c-9546-f2caa1fbf847-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2012-06-15 11:46 ` lei yang
2012-06-15 11:59 ` [git-users] " Vincent van Ravesteijn
[not found] ` <4FDB239A.9070803-0hXrFu2P2+c@public.gmane.org>
2012-06-15 12:56 ` lei yang
2012-06-15 13:11 ` Vincent van Ravesteijn [this message]
[not found] ` <CAHsH0E995C2Fsiyr=MZOH2VyN=mFvnWjrV=6LWkfv-YLy+2RjQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-06-15 12:28 ` Konstantin Khomoutov
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=4FDB349F.3080507@lyx.org \
--to=vfr@lyx.org \
--cc=git@vger.kernel.org \
--cc=yanglei.fage@gmail.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.