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

Re: [PATCH] fetch-pack should not ask for a ref which is already there

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Sep 30, 2005, 12:20 UTC
Message-ID
<Pine.LNX.4.63.0509301418380.15604@wgmdd8.biozentrum.uni-wuerzburg.de>
In-Reply-To
<Pine.LNX.4.64.0509291403050.5362@g5.osdl.org>
Hi,
On Thu, 29 Sep 2005, Linus Torvalds wrote:
Show 18 quoted lines
> On Thu, 29 Sep 2005, Johannes Schindelin wrote:
> > 
> > Wouldn't it make much more sense to add a flag which repairs an 
> > incomplete fetch?
> 
> No.
> 
> We've seen crap. We've _seen_ people use the old git-ssh-pull etc that 
> would result in incomplete repositories, and having people use the 
> "--recover" flag.
> 
> THAT KIND OF CRAP IS UNACCEPTABLE! I had to walk Andrew through a broken 
> repository because he had used those unreliable fetch methods. I was 
> ashamed of git at that point.
> 
> If a ^C results in a repository that needs to be fixed up, the "source 
> control management" is BROKEN. It's not source control, it's a buggy 
> mess.

Okay, fair enough, I had that coming. But how about the opposite? A flag, that says "I want to take the fast path, and if I fsck up, it is my fault alone", just like "-f" to git-checkout?

Ciao, Dscho

Previous: Linus Torvalds
Message 10 of 10 in “fetch-pack should not ask for a ref which is already there”
  1. fetch-pack should not ask for a ref which is already thereJohannes Schindelin, Sep 28, 2005
  2. Junio C HamanoSep 29, 2005
  3. Johannes SchindelinSep 29, 2005
  4. Junio C HamanoSep 29, 2005
  5. Johannes SchindelinSep 29, 2005
  6. Linus TorvaldsSep 29, 2005
  7. Johannes SchindelinSep 29, 2005
  8. Johannes SchindelinSep 29, 2005
  9. Linus TorvaldsSep 29, 2005
  10. Johannes SchindelinSep 30, 2005

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.