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

Re: [PATCH 1/3] push: add --current

From
Paolo Bonzini <bonzini@gnu.org>
Date
Jul 19, 2009, 21:46 UTC
Message-ID
<4A63943E.80209@gnu.org>
In-Reply-To
<20090720063244.6117@nanako3.lavabit.com>
Thanks for the review!
Show 7 quoted lines
> If your final belief (which I happen to agree) is that
> 
> % git push --current
> % git push --current origin
> % git push --current over.there.example.com:project.git
> 
> should work as expected [...] mark clearly that the code after this patch is still broken
Okay, will do.  I just wanted to present both possibilities and thought
that (succeeding) tests were the best way to illustrate the difference.
 For the final submission, now that I had a second opinion, I'll
probably just squash 1/3 and 2/3 together.
Show 7 quoted lines
> The style of the existing tests in the script isn't
> 
> 	test `git rev-parse master` = `cd b.git && git rev-parse master`
> 
> but is
> 
> 	test "$(git rev-parse master)" = "$(cd b.git && git rev-parse master)"
Will do.
Paolo
Previous: Nanako ShiraishiNext: Paolo Bonzini
Message 4 of 6 in “: add git push --current and remote.*.pushHeadOnly”
  1. 0/3 : add git push --current and remote.*.pushHeadOnlyPaolo Bonzini, Jul 13, 2009
  2. 1/3 push: add --currentPaolo Bonzini, Jul 13, 2009
  3. Nanako ShiraishiJul 19, 2009
  4. Paolo BonziniJul 19, 2009
  5. 2/3 change default push refspec when --current is givenPaolo Bonzini, Jul 13, 2009
  6. 3/3 push: add remote.*.pushHeadOnly configurationPaolo Bonzini, Jul 13, 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.