git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Peter Harris <git@peter.is-a-geek.org>
Cc: git@vger.kernel.org
Subject: Re: keeping remote branches in sync
Date: Thu, 9 Oct 2008 08:16:36 -0700	[thread overview]
Message-ID: <20081009151636.GT8203@spearce.org> (raw)
In-Reply-To: <eaa105840810090743pba41a98ocdf79b7c06d76e9e@mail.gmail.com>

Peter Harris <git@peter.is-a-geek.org> wrote:
> On Thu, Oct 9, 2008 at 10:14 AM, Kevin Green wrote:
> > After topic branches are merged to master, we do some cleanup by deleting them
> > from the shared repo.
> >
> > One of the issues we have is that _my_ local repos remote branches aren't kept
> > in sync with the shared repo.
> ...
> 
> > I'd like some comment on whether our workflow could use some improvement.
> > Specifically, if there's a straightforward way to handle the issue above, that
> > would be great.  I've been looking through the manual on git-fetch and
> > git-pull and not seeing any options to do this.
> 
> Is "git remote prune" what you're looking for?

I keep meaning to add "git remote prune" logic into "git fetch",
e.g. as a "git fetch --prune" option.  fetch has all of the data
it needs to implement the prune already in memory, it just doesn't
have the loop to do the prune cleanup.

Now that "git remote" is in C it should be easy to share the prune
code between them, and make this more automatic.

-- 
Shawn.

  reply	other threads:[~2008-10-09 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09 14:14 keeping remote branches in sync Kevin Green
2008-10-09 14:43 ` Peter Harris
2008-10-09 15:16   ` Shawn O. Pearce [this message]
2008-10-09 15:37     ` Kevin Green
2008-10-09 15:46       ` Shawn O. Pearce

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=20081009151636.GT8203@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@peter.is-a-geek.org \
    --cc=git@vger.kernel.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).