From: Taylor Blau <me@ttaylorr.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: Taylor Blau <me@ttaylorr.com>, Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.24.0
Date: Mon, 16 Dec 2019 11:48:28 -0500 [thread overview]
Message-ID: <20191216164828.GA64423@syl.local> (raw)
In-Reply-To: <20191216152047.GQ6527@szeder.dev>
On Mon, Dec 16, 2019 at 04:20:47PM +0100, SZEDER Gábor wrote:
> On Sun, Nov 03, 2019 at 10:23:34PM -0800, Taylor Blau wrote:
> > On Mon, Nov 04, 2019 at 03:18:32PM +0900, Junio C Hamano wrote:
> > > Taylor Blau <me@ttaylorr.com> writes:
> > >
> > > > Thanks for a great release. As always, your release notes were
> > > > very helpful in putting together GitHub's release highlights [1].
> > >
> > > Well, thanks for writing a version readable from humans ;-)
>
> > Please do let me know if you find any other such typos :-).
>
> The commit-graphs section contains a list, with one of the items
> linking to "lots of bug fixes". The last of those links points to
> 2e09c01232 (name-rev: avoid cutoff timestamp underflow, 2019-09-24),
> which isn't in any way related to commit-graphs.
Thanks. I think that this link may have gotten lost in one of the many
shufflings of this blog post. I let one of the blog administrators know
about this, and they should remove the link shortly.
> Better late than never, huh? :)
;-).
Thanks,
Taylor
prev parent reply other threads:[~2019-12-16 16:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 5:36 [ANNOUNCE] Git v2.24.0 Junio C Hamano
2019-11-04 5:49 ` Taylor Blau
2019-11-04 6:18 ` Junio C Hamano
2019-11-04 6:23 ` Taylor Blau
2019-11-04 12:15 ` Philip Oakley
2019-11-04 14:46 ` Elijah Newren
2019-11-04 17:34 ` Taylor Blau
2019-12-16 15:20 ` SZEDER Gábor
2019-12-16 16:48 ` Taylor Blau [this message]
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=20191216164828.GA64423@syl.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=szeder.dev@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.