From: Jeff King <peff@peff.net>
To: Erik Faye-Lund <kusmabite@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH/RFC] remote: support --all for the prune-subcommand
Date: Tue, 4 Oct 2011 03:13:32 -0400 [thread overview]
Message-ID: <20111004071332.GA7308@sigill.intra.peff.net> (raw)
In-Reply-To: <CABPQNSZrfxhyA3em8TN2=d7pAHopZMgRg47baKnDT9h14=rxkA@mail.gmail.com>
On Tue, Oct 04, 2011 at 09:10:40AM +0200, Erik Faye-Lund wrote:
> > git fetch --all --prune
> >
> I wasn't aware that fetch could prune, but yeah, that seems much
> better to me. Perhaps a mention of this in the "git remote prune"
> documentation could steer other users in the right direction?
Yeah, that makes sense.
There is one slight difference: I think "git remote prune" will _just_
prune, and not fetch into existing refs at all. I'm not sure exactly
why you would want that, though. Presumably you run "prune" after you
just fetched, anyway. Combining the two steps saves an extra network
connection.
-Peff
next prev parent reply other threads:[~2011-10-04 7:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 12:16 [PATCH/RFC] remote: support --all for the prune-subcommand Erik Faye-Lund
2011-10-03 18:13 ` Jacob Helwig
2011-10-04 7:00 ` Jeff King
2011-10-04 7:10 ` Erik Faye-Lund
2011-10-04 7:13 ` Jeff King [this message]
2011-10-04 7:18 ` Erik Faye-Lund
2011-10-04 7:40 ` Erik Faye-Lund
2011-10-04 7:56 ` Jeff King
2011-10-04 8:22 ` Erik Faye-Lund
2011-10-12 21:36 ` Jeff King
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=20111004071332.GA7308@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.com \
/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).