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

Re: Allowing push --dry-run through fetch url

From
Mike Hommey <mh@glandium.org>
Date
Nov 6, 2009, 09:53 UTC
Message-ID
<20091106095357.GA13389@glandium.org>
In-Reply-To
<7vfx8s0yy1.fsf@alter.siamese.dyndns.org>

On Fri, Nov 06, 2009 at 01:44:54AM -0800, Junio C Hamano wrote: <snip>

> But doesn't "branch -v" give the necessary information for that purpose
> and even a bit more?  Couldn't "git fetch && git branch -v" be a better
> solution for your real problem "X"?

Usually, when I run git push --dry-run, it's to check that what follows (usually the refspec part) does what I want it to do, such as not pushing tags I didn't intend to push(*), and stuff like that.

Mike

(*) the fact that all tags from all remotes are being mixed doesn't help, here, and without dry-running, I end up pushing tags from one remote onto another.

Previous: Junio C HamanoNext: Junio C Hamano
Message 7 of 11 in “Allowing push --dry-run through fetch url”
  1. Mike HommeyNov 6, 2009
  2. Junio C HamanoNov 6, 2009
  3. Mike HommeyNov 6, 2009
  4. Junio C HamanoNov 6, 2009
  5. Mike HommeyNov 6, 2009
  6. Junio C HamanoNov 6, 2009
  7. Mike HommeyNov 6, 2009
  8. Junio C HamanoNov 8, 2009
  9. Mike HommeyNov 9, 2009
  10. Nanako ShiraishiDec 29, 2009
  11. Junio C HamanoDec 29, 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.