git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: keeping remote branches in sync

From
KGKevin Green <kevin.t.green@morganstanley.com>
Date
Oct 9, 2008, 15:37 UTC
Message-ID
<20081009153738.GJ18241@morganstanley.com>
In-Reply-To
<20081009151636.GT8203@spearce.org>
On 10/09/08 11:16:36, Shawn O. Pearce wrote:
Show 16 quoted lines
> 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?
> 

Yes, it seems to be exactly what we want, though we'd want it just done instead of having to run it ourselves... :)

Show 7 quoted lines
> 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.

That would be great... And a config option to have it done by default each time so '$ git-pull' will just do what we want for our origin remote?

Thanks
--Kevin
Previous: Shawn O. PearceNext: Shawn O. Pearce
Message 4 of 5 in “keeping remote branches in sync”
  1. Kevin GreenOct 9, 2008
  2. Peter HarrisOct 9, 2008
  3. Shawn O. PearceOct 9, 2008
  4. Kevin GreenOct 9, 2008
  5. Shawn O. PearceOct 9, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.