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

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 9, 2019, 19:57 UTC
Message-ID: <xmqqo8zti6oy.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <20190909185829.GA88988@dentonliu-ltm.internal.salesforce.com>

Denton Liu <liu.denton@gmail.com> writes:

Show 15 quoted lines

> 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"?

If you are not convinced it is a good idea, we can easily drop it (and I do not mind dropping it---I am not convinced it is a good idea myself).

Show 11 quoted lines

>> * 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?

OK.  Thanks.