From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: "git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)
Date: Wed, 08 Feb 2017 17:01:41 -0800 [thread overview]
Message-ID: <xmqq37fotbwq.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAGZ79kZ6m1NGz9Lhhd5BDxayLW-UC8MqexMyhHBhHKrmg-tB+w@mail.gmail.com> (Stefan Beller's message of "Wed, 8 Feb 2017 16:25:20 -0800")
Stefan Beller <sbeller@google.com> writes:
>> * sb/submodule-doc (2017-01-12) 3 commits
>> - submodules: add a background story
>> - submodule update documentation: don't repeat ourselves
>> - submodule documentation: add options to the subcommand
>
> The first two commits are good to go IIRC as you seemed to be
> positive about them at the time. Though I have a hard time finding
> evidence of such.
>
> I am currently reworking the 3/3 "add a background story" patch as it is
> RFC-ish, so no need to review that any more.
>
> Maybe we can get 1&2 merged and then 3 comes on its own?
Yeah, sorry, I keep forgetting this topic, it seems. Let's advance
the earlier two. Tentatively I'd drop the third one as you plan to
redo it separately.
Thanks for prodding.
next prev parent reply other threads:[~2017-02-09 1:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 22:34 What's cooking in git.git (Feb 2017, #02; Mon, 6) Junio C Hamano
2017-02-07 0:24 ` SZEDER Gábor
2017-02-07 1:17 ` Jacob Keller
2017-02-07 20:01 ` Junio C Hamano
2017-02-09 0:25 ` Stefan Beller
2017-02-09 1:01 ` Junio C Hamano [this message]
2017-02-09 3:46 ` Jeff King
2017-02-09 5:09 ` Junio C Hamano
2017-02-10 21:17 ` Junio C Hamano
2017-02-09 12:29 ` Johannes Schindelin
2017-02-09 17:20 ` Junio C Hamano
2017-02-09 20:37 ` Johannes Schindelin
2017-02-09 22:02 ` Junio C Hamano
2017-02-09 22:32 ` Johannes Schindelin
2017-02-09 16:08 ` Michael Haggerty
2017-02-09 19:18 ` Junio C Hamano
2017-02-09 19:24 ` 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=xmqq37fotbwq.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.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 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 NNTP newsgroup(s).