From: Philip Oakley <philipoakley@iee.org>
To: Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2019, #05; Thu, 30)
Date: Sun, 2 Jun 2019 18:48:41 +0100 [thread overview]
Message-ID: <45a46a7a-8fdb-dac3-37bf-79569cd4d600@iee.org> (raw)
In-Reply-To: <xmqq5zpqwms1.fsf@gitster-ct.c.googlers.com>
On 31/05/2019 18:34, Junio C Hamano wrote:
>>> * po/git-help-on-git-itself (2019-05-16) 2 commits
>>> - Doc: git.txt: remove backticks from link and add git-scm.com/docs
>>> - git.c: show usage for accessing the git(1) help page
>>>
>>> "git help git" was hard to discover (well, at least for some
>>> people).
>>>
>>> Will merge to 'next'.
>> I guess it would not hurt anybody (and get a bit more exposure) if it was
>> merged before v2.22.0, but it does not fix a problem introduced in this
>> cycle, so...
> Yeah, I think you already know this but my stance towards these
> "would never hurt to merge even in -rc period" topics is to merge
> them soon after the final.
>
I'm perfectly happy with this. As a small patch I thought it worth
'getting started promptly', even if it was in the early rc period, and
I'm happy to wait and let the wheels turn steadily.
--
Philip
next prev parent reply other threads:[~2019-06-02 17:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 21:23 What's cooking in git.git (May 2019, #05; Thu, 30) Junio C Hamano
2019-05-31 11:39 ` Johannes Schindelin
2019-05-31 17:02 ` Junio C Hamano
2019-05-31 17:14 ` Johannes Schindelin
2019-05-31 12:42 ` Johannes Schindelin
2019-05-31 17:34 ` Junio C Hamano
2019-05-31 18:48 ` Johannes Schindelin
2019-06-01 15:08 ` Kaartic Sivaraam
2019-06-02 17:48 ` Philip Oakley [this message]
2019-05-31 18:56 ` Junio C Hamano
2019-05-31 20:26 ` cc/list-objects-filter-wo-sparse-path, was " Johannes Schindelin
2019-06-02 14:32 ` Jiang Xin
2019-06-05 18:38 ` Nickolai Belakovski
2019-06-06 13:09 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45a46a7a-8fdb-dac3-37bf-79569cd4d600@iee.org \
--to=philipoakley@iee.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).