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

Re: What's cooking in git.git (Jul 2009, #02; Sun, 26)

From
Paolo Bonzini <paolo.bonzini@gmail.com>
Date
Jul 28, 2009, 08:09 UTC
Message-ID
<4A6EB22F.6090007@gmail.com>
In-Reply-To
<7v3a8h8cdc.fsf@alter.siamese.dyndns.org>
On 07/28/2009 10:01 AM, Junio C Hamano wrote:
> The last thing I want to do is to give end users
> a set of new command line options in 'master' (or even 'next'), only to
> revoke them before the next release.

Agreed. However, some people expressed appreciation for the new git-push command-line option independent of the push.tracking work, of which I'd guess they might not even be aware. If you agree, I would leave in pu the third patch ("add remote.*.pushHeadOnly") while merging the first two to next.

Paolo
Previous: Junio C Hamano
Message 11 of 11 in “What's cooking in git.git (Jul 2009, #02; Sun, 26)”
  1. Junio C HamanoJul 26, 2009
  2. Jakub NarebskiJul 26, 2009
  3. en/fast-export, was Re: What's cooking in git.git (Jul 2009, #02; Sun, 26)Johannes Schindelin, Jul 26, 2009
  4. db/transport-shim, was Re: What's cooking in git.git (Jul 2009, #02; Sun, 26)Johannes Schindelin, Jul 26, 2009
  5. Michael HaggertyJul 26, 2009
  6. gp/maint-rebase-p-onto, was Re: What's cooking in git.git (Jul 2009, #02; Sun, 26)Johannes Schindelin, Jul 26, 2009
  7. Johannes SchindelinJul 26, 2009
  8. Alex RiesenJul 27, 2009
  9. Paolo BonziniJul 28, 2009
  10. Junio C HamanoJul 28, 2009
  11. Paolo BonziniJul 28, 2009

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.