From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2017, #04; Tue, 13)
Date: Thu, 15 Jun 2017 08:54:41 -0700 [thread overview]
Message-ID: <xmqqo9tp2qm6.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170614005247.GT133952@aiede.mtv.corp.google.com> (Jonathan Nieder's message of "Tue, 13 Jun 2017 17:52:47 -0700")
Jonathan Nieder <jrnieder@gmail.com> writes:
>> It is not known if a simple "yes/no" is sufficient in the longer
>> term, and what should happen when --recurse-submodules option starts
>> taking "recurse into them how?" parameter, though.
>
> Any pointers for where this has been discussed, if anywhere (e.g. was
If this were discussed, then the answer to the question we may know
by now ;-) I do not think anybody gave a serious thought to convince
the public why a boolean is enough, hence this comment.
>> * bw/config-h (2017-06-13) 4 commits
>> - config: don't implicitly use gitdir
>> - config: don't include config.h by default
>> - config: remove git_config_iter
>> - config: create config.h
>>
>> Code clean-up.
>
> Patches 1-3 are good to go IMHO.
>
> Patch 4 in pu is marked with my Reviewed-by. I think it's getting
> there but not there yet. Did some script pull the tag from my reply
> to the cover letter?
No, nothing that elaborate.
I go through each message in Gnus newsreader and feed the article to
a shell command, e.g. "Meta/add-by -r jrnieder@ | git am -s3c". The
UI remembers the last command I used when I choose to feed the next
article to a shell command, and after running it to first three, I
forgot to remove the 'add-by' bit from the command line for the fourth
one.
next prev parent reply other threads:[~2017-06-15 15:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 21:40 What's cooking in git.git (Jun 2017, #04; Tue, 13) Junio C Hamano
2017-06-14 0:52 ` Jonathan Nieder
2017-06-15 15:54 ` Junio C Hamano [this message]
2017-06-14 7:42 ` Lars Schneider
2017-06-14 18:38 ` Torsten Bögershausen
2017-06-14 10:57 ` rs/strbuf-addftime-zZ, was " Johannes Schindelin
2017-06-14 11:10 ` Jeff King
2017-06-14 19:36 ` René Scharfe
2017-06-14 21:04 ` Johannes Schindelin
2017-06-14 23:03 ` René Scharfe
2017-06-15 5:42 ` Jeff King
2017-06-15 8:46 ` René Scharfe
2017-06-14 18:23 ` 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
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=xmqqo9tp2qm6.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@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.
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).