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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 29, 2009, 16:58 UTC
Message-ID
<7v1vidhg40.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20091229200517.6117@nanako3.lavabit.com>
Nanako Shiraishi <nanako3@lavabit.com> writes:
Show 9 quoted lines
> Junio, could you tell us what happened to this thread?
>
> After discussing "git push --dry-run" that looks at URL used for
> fetching, because pushURL might require authentication, the
> maintainer recalls an earlier "git push --confirm" patch
>
> http://thread.gmane.org/gmane.comp.version-control.git/128426/focus=128429
>
> but nothing happens after that.
Your analysis is correct --- nothing happened after that ;-)

I think it is probably worthwhile to revisit Owen's patch, though. Back then I was worried too much about giving IDE authors (who need to scrape the output and interact with the "confirm" interface) enough flexibility and wanted to see an interface to allow plugging a more machine readable interaction before proceeding, but I changed my mind.

We can have --confirm with two output styles, one that is for consumption by human sitting in front of a terminal (and is prone to future UI tinkering like coloring), and the other with machine readable interaction, that is more or less frozen (or "extensible"). And it is perfectly Ok to start only with the human readable one, clearly documented that it is not (yet) for use by IDE via scraping.

But I won't be the person with the --confirm itch, so interested people need to help to make that happen.

Thanks for a stream of reminders, by the way.
Previous: Nanako Shiraishi
Message 11 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.