Re: What's cooking in git.git (Apr 2019, #05; Thu, 25)
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Apr 26, 2019, 06:01 UTC
- Message-ID
- <xmqq8svxuwyi.fsf@gitster-ct.c.googlers.com>
- In-Reply-To
- <20190426055335.GA16651@Taylors-MBP.hsd1.wa.comcast.net>
Taylor Blau <me@ttaylorr.com> writes:
Show 10 quoted lines
> Ah, I _can_ see the merge in my local copy (fetched from > https://github.com/git/git) as c49927fca0 (Merge branch 'tb/unexpected' > into next, 2019-04-25). > > I looked for the commits themselves with: > > $ git log --author=Taylor > > on 'next', but only found the first four. I'm sure there's a logical > explanation of why this happened, but I'm not sure what it is :-).
The last three patches were made out of these messages from you
Message-Id: <e0bd479e822ce81de280ee6fdd07f608a96b7836.1554861974.git.me@ttaylorr.com> Message-Id: <88ca5dfe68c4cdb558aff6e90a525ec06f15dbd6.1554861974.git.me@ttaylorr.com> Message-Id: <e9400a9f773adb62315f75347ad7231b4476a2f4.1554861974.git.me@ttaylorr.com>
These were you relaying Peff's commits, for example, the topmost one
https://public-inbox.org/git/e0bd479e822ce81de280ee6fdd07f608a96b7836.1554861974.git.me@ttaylorr.com/
begins with an in-body header From: with a corresponding sign-off, both by Peff.