From: lei yang <yanglei.fage-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Vincent van Ravesteijn <vfr-0hXrFu2P2+c@public.gmane.org>
Cc: git-users-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
tfnico-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Re: how to get the formated patches from the merge id
Date: Fri, 15 Jun 2012 20:56:28 +0800 [thread overview]
Message-ID: <CAHsH0E8MzMW8SEFGB_X80qH_5btnmvLWFxjQ-EBSaGbHSUz-Sg@mail.gmail.com> (raw)
In-Reply-To: <4FDB239A.9070803-0hXrFu2P2+c@public.gmane.org>
On Fri, Jun 15, 2012 at 7:59 PM, Vincent van Ravesteijn <vfr-0hXrFu2P2+c@public.gmane.org> wrote:
> Op 15-6-2012 13:46, lei yang schreef:
>
>> Hi
>>
>> I mean,
>>
>> I have a commit like below
>> commit 0e93b4b304ae052ba1bc73f6d34a68556fe93429
>> Merge: b724cc1 51bfd29
>>
>> This commit done this work: merge b724cc1..51bfd29 commit,
>>
>> The question is how could I *onlys* through
>> 0e93b4b304ae052ba1bc73f6d34a68556fe93429 to get the formated patch for
>> the
>> commit(b724cc1..51bfd29)
>
>
> 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"
so this do the same thing, formated patch which merged, can you give a
try to explain it in your workspace. and I don't understand what you
said "branch 51bfd29",51bfd29 is not the branch
Thanks for your help,git format-patch 0e93b4b3^1..0e93b4b3^2 is what I need.
Lei
> If this is really what you want you can do:
>
> $ git format-patch 0e93b4b3^1..0e93b4b3^2
>
> 0e93b4b3^1 means the first parent of 0e93b4b3, which is b724cc1. 0e93b4b3^2
> means the second parent, which is 51bfd29
>
> HTH,
>
> Vincent
--
You received this message because you are subscribed to the Google Groups "Git for human beings" group.
To post to this group, send email to git-users-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to git-users+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
next prev parent reply other threads:[~2012-06-15 12:56 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 [this message]
2012-06-15 13:11 ` Vincent van Ravesteijn
[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=CAHsH0E8MzMW8SEFGB_X80qH_5btnmvLWFxjQ-EBSaGbHSUz-Sg@mail.gmail.com \
--to=yanglei.fage-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=git-users-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=tfnico-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=vfr-0hXrFu2P2+c@public.gmane.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 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).