From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] Teach 'git remote' how to cleanup stale tracking branches.
Date: Fri, 2 Feb 2007 01:13:59 -0500 [thread overview]
Message-ID: <20070202061359.GB20719@spearce.org> (raw)
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.
next prev parent reply other threads:[~2007-02-02 6:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58b74d176fd10417a58d42d9437c631d03f4c4f6.1170392736.git.spearce@spearce.org>
2007-02-02 5:06 ` [PATCH 2/2] Teach 'git remote' how to cleanup stale tracking branches Shawn O. Pearce
2007-02-02 6:06 ` Junio C Hamano
2007-02-02 6:13 ` Shawn O. Pearce [this message]
2007-02-02 10:53 ` Jakub Narebski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070202061359.GB20719@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).