From: Taylor Blau <me@ttaylorr.com>
To: Elijah Newren <newren@gmail.com>
Cc: Philip Oakley <philipoakley@iee.email>,
Taylor Blau <me@ttaylorr.com>, Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git v2.24.0
Date: Mon, 4 Nov 2019 09:34:26 -0800 [thread overview]
Message-ID: <20191104173426.GA68471@syl.local> (raw)
In-Reply-To: <CABPp-BHJ3eAARDAdbKZcGwMPSL7f7XD=7as0igvoPM8f8ODhUA@mail.gmail.com>
On Mon, Nov 04, 2019 at 06:46:12AM -0800, Elijah Newren wrote:
> On Mon, Nov 4, 2019 at 4:18 AM Philip Oakley <philipoakley@iee.email> wrote:
> > On 04/11/2019 06:23, 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].
> > > Ah, thanks. It must have been dropped in one of the rounds of review. I
> > > added it back.
> > >
> > > Please do let me know if you find any other such typos :-).
> >
> > in the tidbits section there are two places where a double-dash 'option'
> > is shown with only a single dash:
> >
> > -super-dangerous-option
> > -end-of-options
Fixed!
> There's a similar issue earlier in the notes where --analyze has had
> one of it's dashes dropped so it appears as only -analyze.
...and fixed! Sorry both.
Thanks,
Taylor
next prev parent reply other threads:[~2019-11-04 17:34 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 [this message]
2019-12-16 15:20 ` SZEDER Gábor
2019-12-16 16:48 ` Taylor Blau
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=20191104173426.GA68471@syl.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
--cc=philipoakley@iee.email \
/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.