git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: "Philip Jägenstedt" <philip@foolip.org>
Cc: Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, "martin f. krafft" <madduck@debian.org>
Subject: Re: Working with remotes with (too) many branches
Date: Tue, 21 Feb 2012 16:43:03 -0600	[thread overview]
Message-ID: <20120221224303.GB31934@burratino> (raw)
In-Reply-To: <CAKHWUkY_bEtKoPOiWFz6i2bp-tbekapROOaCYR0k5Ymh0HYMdA@mail.gmail.com>

Hi Philip,

Philip Jägenstedt wrote:

> It seems to me that if one starts out with all branches and then
> "set-branches main footopic", one really does want all other refs to
> go away on the next fetch.

I would expect set-branches to remove the remote-tracking branches
that are no longer relevant itself, actually.

Martin, does this seem sensible to you?  If so, I'll be happy to look
into it in the next few days (or I'll be even happier someone else
gets to it first).

Hope that helps,
Jonathan

  reply	other threads:[~2012-02-21 22:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-19 15:29 Working with remotes with (too) many branches Philip Jägenstedt
2012-02-19 21:36 ` Junio C Hamano
2012-02-21 22:36   ` Philip Jägenstedt
2012-02-21 22:43     ` Jonathan Nieder [this message]
2012-02-21 22: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=20120221224303.GB31934@burratino \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=madduck@debian.org \
    --cc=philip@foolip.org \
    /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).