From: demerphq <demerphq@gmail.com>
To: Finn Arne Gangstad <finnag@pvv.org>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] git remote update: New option --prune (-p)
Date: Thu, 2 Apr 2009 15:34:15 +0200 [thread overview]
Message-ID: <9b18b3110904020634i17633645ue4ba91701ea243a1@mail.gmail.com> (raw)
In-Reply-To: <20090402123823.GA1756@pvv.org>
2009/4/2 Finn Arne Gangstad <finnag@pvv.org>:
> With the --prune (or -p) option, git remote update will also prune
> all the remotes that it fetches. Previously, you had to do a manual git
> remote prune <remote> for each of the remotes you wanted to prune, and this
> could be tedious with many remotes.
Yay!
But one question. It seem to me odd to put this as an option to git
remote update, and not git remote prune.
I mean, it seems weird that one must say:
git remote update --prune
and one cannot say:
git remote prune --all
especially when there is a `git remote prune` already. It seems a bit
counterintuitive to find pruning actions under "update", but not all
that strange to find an all "--all" option for the "prune" action.
Although to me having both be allowed and mean the same thing also makes sense.
Anyway, thanks for this regardless, I am looking forward to this
functionality. :-)
Cheers,
yves
--
perl -Mre=debug -e "/just|another|perl|hacker/"
next prev parent reply other threads:[~2009-04-02 13:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 12:38 [PATCH] git remote update: New option --prune (-p) Finn Arne Gangstad
2009-04-02 13:34 ` demerphq [this message]
2009-04-02 13:44 ` Jeff King
2009-04-02 14:17 ` demerphq
2009-04-02 14:31 ` Jeff King
2009-04-02 16:07 ` demerphq
2009-04-02 16:32 ` Jeff King
2009-04-02 19:05 ` demerphq
2009-04-02 18:06 ` Junio C Hamano
2009-04-02 20:18 ` Finn Arne Gangstad
2009-04-02 20:52 ` Junio C Hamano
2009-04-03 9:00 ` [PATCHv2 0/2] " Finn Arne Gangstad
2009-04-03 9:02 ` [PATCHv2 1/2] builtin-remote.c: Split out prune_remote as a separate function Finn Arne Gangstad
2009-04-03 9:03 ` [PATCHv2 2/2] git remote update: New option --prune Finn Arne Gangstad
2009-04-05 9:47 ` Junio C Hamano
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=9b18b3110904020634i17633645ue4ba91701ea243a1@mail.gmail.com \
--to=demerphq@gmail.com \
--cc=finnag@pvv.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).