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:00:06 -0400 [thread overview]
Message-ID: <20111004070006.GA6824@sigill.intra.peff.net> (raw)
In-Reply-To: <1317644168-5808-1-git-send-email-kusmabite@gmail.com>
On Mon, Oct 03, 2011 at 02:16:08PM +0200, Erik Faye-Lund wrote:
> I recently needed to prune remote branches in a repo with a lot
> of remotes, and to my surprise "git remote prune" didn't support
> the --all option. So I added it. Perhaps this is useful for other
> people as well?
You could do:
git remote update --prune
But I thought we were trying to get away from remote doing fetch-like
things in the long term. Isn't the "right" way to do this these days:
git fetch --all --prune
?
-Peff
next prev parent reply other threads:[~2011-10-04 7:00 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 [this message]
2011-10-04 7:10 ` Erik Faye-Lund
2011-10-04 7:13 ` Jeff King
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=20111004070006.GA6824@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).