git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Denton Liu <liu.denton@gmail.com>
Date
Sep 9, 2019, 18:58 UTC
Message-ID
<20190909185829.GA88988@dentonliu-ltm.internal.salesforce.com>
In-Reply-To
<xmqqd0gcm2zm.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Sat, Sep 07, 2019 at 10:26:53AM -0700, Junio C Hamano wrote:
Show 9 quoted lines
> * 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"?

Show 7 quoted lines
> 
> * 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/`.

Show 9 quoted lines
> * 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.

Show 9 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?
Thanks,
Denton
Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 16 in “What's cooking in git.git (Sep 2019, #01; Sat, 7)”
  1. Junio C HamanoSep 7, 2019
  2. Denton LiuSep 9, 2019
  3. Junio C HamanoSep 9, 2019
  4. Denton LiuSep 10, 2019
  5. brian m. carlsonSep 9, 2019
  6. Junio C HamanoSep 10, 2019
  7. Junio C HamanoSep 28, 2019
  8. brian m. carlsonSep 28, 2019
  9. Martin ÅgrenSep 10, 2019
  10. Josh SteadmonSep 10, 2019
  11. Matheus Tavares BernardinoSep 11, 2019
  12. pd/fetch-jobs, was Re: What's cooking in git.git (Sep 2019, #01; Sat, 7)Johannes Schindelin, Sep 11, 2019
  13. Junio C HamanoSep 12, 2019
  14. Palmer DabbeltSep 14, 2019
  15. Junio C HamanoSep 16, 2019
  16. Palmer DabbeltSep 16, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.