Re: Re: how to get the formated patches from the merge id
- From
- Konstantin Khomoutov <flatworm-rn4veauk+akrv+lv9mx5uipxlwaovq5f@public.gmane.org>
- Date
- Jun 15, 2012, 12:28 UTC
- Message-ID
- <20120615162842.90e63870.kostix@domain007.com>
- In-Reply-To
- <CAHsH0E995C2Fsiyr=MZOH2VyN=mFvnWjrV=6LWkfv-YLy+2RjQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, 15 Jun 2012 19:46:22 +0800 lei yang <yanglei.fage-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
Show 5 quoted lines
> I have a commit like below > commit 0e93b4b304ae052ba1bc73f6d34a68556fe93429 > Merge: b724cc1 51bfd29 > > This commit done this work: merge b724cc1..51bfd29 commit,
This is a gross misunderstanding of how revision ranges work in Git. Please read the "gitrevisions" manual page. More precisely, the A..B notation means "All commits reachable from B excluding those reachable from A". A merge means that two lines of history (those ending with commits b724cc1 and 51bfd29, respectively) are merged together. Writing this as b724cc1..51bfd29 is incorrect and confusing for the readers.
> The question is how could I *onlys* through > 0e93b4b304ae052ba1bc73f6d34a68556fe93429 to get the formated patch for > the commit(b724cc1..51bfd29)
This phrase again missies a predicate (a verb) so we consistently fail to comprehend your intent. You could try to find a colleague with a bit better English skill and ask his/her to provide a better translation so we're able to understan it. Also try to get rid of that ".." notation as it seems to ruin your attempts to get us understand the matter.
-- 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.