Jonathan Nieder <jrnie...@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.

Reply via email to