From: Jeff King <peff@peff.net>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [RFC/PATCH 0/3] push: add 'prune' option
Date: Tue, 21 Feb 2012 12:35:48 -0500 [thread overview]
Message-ID: <20120221173548.GB32376@sigill.intra.peff.net> (raw)
In-Reply-To: <CACsJy8ACoF=2dEUoFvT8bQDmUsjJA2_VWvTSJV6fakqyCLBCYg@mail.gmail.com>
On Tue, Feb 21, 2012 at 10:30:31PM +0700, Nguyen Thai Ngoc Duy wrote:
> On Sat, Feb 18, 2012 at 2:12 AM, Felipe Contreras
> <felipe.contreras@gmail.com> wrote:
> > As an example I put my use-case; I want to backup *all* my local branches to a
> > personal repository, and I want to remove branches that I have removed from my
> > local repository. git push personal 'refs/heads/*' mostly does the job, but it
> > doesn't remove anything, and that's where 'prune' comes from.
>
> Yeah, may I have "fetch --prune" too, please? Looking at diffstat
> gives me a feeling that you only need to add maybe four lines to
> builtin/fetch.c and my dream would come true.
Huh? Don't we already have "fetch --prune"?
-Peff
next prev parent reply other threads:[~2012-02-21 17:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 19:12 [RFC/PATCH 0/3] push: add 'prune' option Felipe Contreras
2012-02-17 19:12 ` [RFC/PATCH 1/3] remote: use a local variable in match_push_refs() Felipe Contreras
2012-02-17 22:31 ` Junio C Hamano
2012-02-17 19:12 ` [RFC/PATCH 2/3] remote: reorganize check_pattern_match() Felipe Contreras
2012-02-17 22:34 ` Junio C Hamano
2012-02-22 20:15 ` Felipe Contreras
2012-02-22 21:02 ` Junio C Hamano
2012-02-17 19:12 ` [RFC/PATCH 3/3] push: add 'prune' option Felipe Contreras
2012-02-17 22:25 ` Jeff King
2012-02-17 22:34 ` Junio C Hamano
2012-02-22 20:43 ` Felipe Contreras
2012-02-22 20:56 ` Junio C Hamano
2012-02-22 23:06 ` Felipe Contreras
2012-02-22 23:54 ` Junio C Hamano
2012-02-21 15:30 ` [RFC/PATCH 0/3] " Nguyen Thai Ngoc Duy
2012-02-21 17:35 ` Jeff King [this message]
2012-02-22 1:45 ` Nguyen Thai Ngoc Duy
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=20120221173548.GB32376@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@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).