Re: What's cooking in git.git (Sep 2019, #01; Sat, 7)

[Denton Liu <liu.denton@gmail.com>]

Hi Junio,

On Sat, Sep 07, 2019 at 10:26:53AM -0700, Junio C Hamano wrote:
> * dl/complete-cherry-pick-revert-skip (2019-08-27) 3 commits
>  - status: mention --skip for revert and cherry-pick
>  - completion: add --skip for cherry-pick and revert
>  - completion: merge options for cherry-pick and revert
> 
>  The command line completion support (in contrib/) learned about the
>  "--skip" option of "git revert" and "git cherry-pick".
> 
>  Will merge to 'next'.

Did we end up deciding whether or not we were going to drop "status:
mention --skip for revert and cherry-pick"?

> 
> * dl/use-sq-from-test-lib (2019-09-06) 1 commit
>  - t: use common $SQ variable
> 
>  Code cleanup.
> 
>  Will merge to 'next'.

This needs a tiny update to its commit message: we should change 
`git grep =\\\\\'` to `git grep =\\\\\' t/`.

> * dl/format-patch-cover-letter-subject (2019-09-05) 1 commit
>  - format-patch: learn --infer-cover-subject option
>  (this branch uses dl/format-patch-doc-test-cleanup.)
> 
>  "git format-patch --cover-letter" learned to optionally use the
>  first paragraph (typically a single-liner) of branch.*.description
>  as the subject of the cover letter.
> 
>  Reroll with a redesign with less emphasis on "subject" coming?

Correct, I'll wait for the format-patch cleanup stuff to settle down
before sending the reroll in.

> * dl/remote-save-to-push (2018-12-11) 1 commit
>  - remote: add --save-to-push option to git remote set-url
> 
>  "git remote set-url" learned a new option that moves existing value
>  of the URL field to pushURL field of the remote before replacing
>  the URL field with a new value.
> 
>  Anybody who wants to champion this topic?
>  I am personally not yet quite convinced if this is worth pursuing.

Perhaps it's time to drop this topic?

Thanks,

Denton