From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Josh Triplett <josh@joshtriplett.org>, git@vger.kernel.org
Subject: Re: Cross-referencing the Git mailing list archive with their corresponding commits in `pu`
Date: Mon, 20 Feb 2017 11:33:24 -0800 [thread overview]
Message-ID: <xmqqefysk67v.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1702171841450.3496@virtualbox> (Johannes Schindelin's message of "Fri, 17 Feb 2017 18:50:00 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> There is a third category, and this one *does* come as a surprise to me.
> It appears that at least *some* patches' Date: lines are either ignored or
> overridden or changed on their way from the mailing list into Git's commit
> history. There was only one commit in that commit range:
>
> 3c0cb0c (read_loose_refs(): read refs using resolve_ref_recursively(),
> Michael Haggerty 2017-02-09)
>
> This one was committed with an author date "Thu, 09 Feb 2017 21:53:52
> +0100" but it appears that there was no mail sent to the Git mailing list
I think this is this one:
<ff0b0df6-9aed-9417-d9d4-1234d53f05c3@alum.mit.edu>
Recent "What's cooking" lists the topic this one is part with this
comment:
The tip one is newer than the one posted to the list but was sent
privately by the author via his GitHub repository.
next prev parent reply other threads:[~2017-02-20 19:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 15:34 Cross-referencing the Git mailing list archive with their corresponding commits in `pu` Johannes Schindelin
2017-02-06 19:10 ` Junio C Hamano
2017-02-09 14:11 ` Lars Schneider
2017-02-09 21:53 ` Johannes Schindelin
2017-02-09 22:18 ` Junio C Hamano
2017-02-06 20:48 ` Eric Wong
2017-02-06 22:07 ` Jeff King
2017-02-07 0:14 ` Eric Wong
2017-02-17 17:50 ` Johannes Schindelin
2017-02-20 19:33 ` Junio C Hamano [this message]
2017-02-20 20:06 ` Junio C Hamano
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=xmqqefysk67v.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=josh@joshtriplett.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 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.