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, 08:59 UTC
Message-ID
<20091106085917.GA497@glandium.org>
In-Reply-To
<7vtyx82g2a.fsf@alter.siamese.dyndns.org>
On Fri, Nov 06, 2009 at 12:49:49AM -0800, Junio C Hamano wrote:
> The daemon sitting on the other end to serve "git://" URL won't understand
> an attempt to push into.  What goes over the wire in the fetch protocol
> does not give your updated "git push" enough information to guess what
> would happen if you pushed.

Maybe I'm missing something, but the only missing thing I can see at first thought is whether the server is going to reject non fast-forward updates. Are there any others ?

Mike
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 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.