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

Re: [PATCH 2/2] Teach 'git remote' how to cleanup stale tracking branches.

From
Shawn O. Pearce <spearce@spearce.org>
Date
Feb 2, 2007, 06:13 UTC
Message-ID
<20070202061359.GB20719@spearce.org>
In-Reply-To
<7v4pq5ks9i.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> If you are disconnected, would it fail gracefully without
> removing stuff?  From a cursory look it should, but just making
> sure.
Indeed, it crashes out:
 
	$ ./git-remote prune cs-src
	ssh: host.that.exists: No address associated with nodename
	fatal: The remote end hung up unexpectedly
	ls-remote --heads cs:sw/src/git: command returned error: 1
	[git (sp/remote)]$ ls .git/refs/remotes/cs-src/
	.       ..      master
and the refs are still safe.
-- 
Shawn.
Previous: Junio C HamanoNext: Jakub Narebski
Message 3 of 4 in “Teach 'git remote' how to cleanup stale tracking branches.”
  1. 2/2 Teach 'git remote' how to cleanup stale tracking branches.Shawn O. Pearce, Feb 2, 2007
  2. Junio C HamanoFeb 2, 2007
  3. Shawn O. PearceFeb 2, 2007
  4. Jakub NarebskiFeb 2, 2007

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.