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

Re: Bug report: stash in upstream caused remote fetch to fail

From
AWAndrew Walrond <andrew@walrond.org>
Date
Feb 1, 2012, 22:37 UTC
Message-ID
<20120201223743.GC2431@localhost.localdomain>
In-Reply-To
<874nvap9hj.fsf@thomas.inf.ethz.ch>
On Wed, Feb 01, 2012 at 09:46:48PM +0100, Thomas Rast wrote:
Show 5 quoted lines
> 
> Do you, by any chance, still have a copy of the upstream repo before you
> trashed the stash?  It would be interesting to know whether there was
> actually some repository corruption going on (that went unnoticed by
> fsck, no less) or if there was a bug in the transmission.

I tried to reproduce the problem but without success :( Disk corruption is unlikely - raided drives etc etc. More likely stash related somehow as I was applying patches manually on older versions checked out in a temp branch, stashing the results then applying the stash onto master/HEAD. But why was a remote clone involved with the upstream stash at all I wonder??

Andrew Walrond
Previous: Andrew Walrond
Message 2 of 2 in “Bug report: stash in upstream caused remote fetch to fail”
  1. Andrew WalrondFeb 1, 2012
  2. Andrew WalrondFeb 1, 2012

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.