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

Re: Catching up: git-pasky-0.6.2 broken?

From
Petr Baudis <pasky@ucw.cz>
Date
Apr 23, 2005, 21:25 UTC
Message-ID
<20050423212505.GB13222@pasky.ji.cz>
In-Reply-To
<20050423151238.C32116@flint.arm.linux.org.uk>

Dear diary, on Sat, Apr 23, 2005 at 04:12:39PM CEST, I got a letter where Russell King <rmk@arm.linux.org.uk> told me that...

> Could the problem be related to some random garbage left in .git/add-queue
> and .git/rm-queue?
Quite likely.
> If so, how did these files get generated in the first place, and why
> weren't they removed when they were finished with?
That was a bug in git apply, fixed for quite some time already.
> IMHO updating a repository from an external source should _NOT_ be
> affected by the presence (or absense) of these two files, which
> contain only _local_ state information.

Note that the latest git-pasky (post-0.6.3) is already completely queues-free.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
Previous: Martin Schlemmer
Message 5 of 5 in “Catching up: git-pasky-0.6.2 broken?”
  1. Russell KingApr 23, 2005
  2. Russell KingApr 23, 2005
  3. Russell KingApr 23, 2005
  4. Martin SchlemmerApr 23, 2005
  5. Petr BaudisApr 23, 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.