git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Robin Rosenberg <robin.rosenberg@dewire.com>
Cc: git@vger.kernel.org
Subject: [JGIT PATCH 0/6] Add prune of stale tracking branches to fetch
Date: Thu, 12 Feb 2009 15:54:34 -0800	[thread overview]
Message-ID: <1234482880-1316-1-git-send-email-spearce@spearce.org> (raw)

This series teaches "jgit fetch" how to prune stale tracking branches
that have been removed from the remote repository.  We can now do
both a fetch and a prune in a single network connection.

I wanted to also add this for push, but its going to be more complex.
The RefSpec data I need isn't available in the PushProcess code path,
and the Transport.push() method isn't doing me any favors at making
it available to me.

I need to move on to some other things today, so I'm posting this
fetch series now as this looks good as-is.

Shawn O. Pearce (6):
  Fix RefUpdate.delete to update the result status
  Add setBoolean, setInt to RepositoryConfig
  Add RefSpec.expandFromDestination for reverse mappings
  Add the remote.name.mirror flag to RemoteConfig
  Don't pass TagOpt to FetchProcess, get it from the Transport
  Teach fetch to prune stale tracking branches

 .../org/spearce/jgit/pgm/AbstractFetchCommand.java |    8 ++-
 .../src/org/spearce/jgit/pgm/Fetch.java            |    9 +++
 .../spearce/jgit/transport/RefSpecTestCase.java    |   22 ++++++
 .../src/org/spearce/jgit/lib/RefUpdate.java        |    4 +-
 .../src/org/spearce/jgit/lib/RepositoryConfig.java |   57 +++++++++++++++
 .../org/spearce/jgit/transport/FetchProcess.java   |   55 +++++++++++++--
 .../src/org/spearce/jgit/transport/RefSpec.java    |   73 ++++++++++++++------
 .../org/spearce/jgit/transport/RemoteConfig.java   |   40 +++++++++++-
 .../src/org/spearce/jgit/transport/Transport.java  |   29 ++++++++-
 9 files changed, 265 insertions(+), 32 deletions(-)

             reply	other threads:[~2009-02-12 23:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12 23:54 Shawn O. Pearce [this message]
2009-02-12 23:54 ` [JGIT PATCH 1/6] Fix RefUpdate.delete to update the result status Shawn O. Pearce
2009-02-12 23:54   ` [JGIT PATCH 2/6] Add setBoolean, setInt to RepositoryConfig Shawn O. Pearce
2009-02-12 23:54     ` [JGIT PATCH 3/6] Add RefSpec.expandFromDestination for reverse mappings Shawn O. Pearce
2009-02-12 23:54       ` [JGIT PATCH 4/6] Add the remote.name.mirror flag to RemoteConfig Shawn O. Pearce
2009-02-12 23:54         ` [JGIT PATCH 5/6] Don't pass TagOpt to FetchProcess, get it from the Transport Shawn O. Pearce
2009-02-12 23:54           ` [JGIT PATCH 6/6] Teach fetch to prune stale tracking branches Shawn O. Pearce
2009-02-13  0:37 ` [JGIT PATCH 0/6] Add prune of stale tracking branches to fetch Junio C Hamano
2009-02-13  0:42   ` Shawn O. Pearce
2009-02-13  0:48     ` 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=1234482880-1316-1-git-send-email-spearce@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=robin.rosenberg@dewire.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).