git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Björn Gustavsson" <bgustavsson@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [RFC/PATCH 0/4] Re-implement 'remote update' using 'fetch'
Date: Sun, 08 Nov 2009 16:44:52 +0100	[thread overview]
Message-ID: <4AF6E774.80909@gmail.com> (raw)

After having done my previous patch to implement 'git fetch --all'
I decided to implement as much functionality in 'git fetch' to
make it possibility to re-implement 'git remote update' in terms of
'git fetch'.

The following things are currently missing from the patch series:

* updated documentation
* test cases for the group functionality in fetch
* support for 'git remote update --prune'

There is also a slight backward incompatibility that I know of (see the commit
message for the last commit). I could fix that, if there are
people depending on it.

I have no idea how much of the group functionality is really used. If someone
knows that "no-one uses THIS feature and" it would be nice to know.

Björn Gustavsson (4):
  Teach the --all option to 'git fetch'
  Teach the --multiple option to 'git fetch'
  Add the configure variable skipFetchAll
  Re-implement 'git remote update' using 'git fetch'

 Documentation/git-fetch.txt |    5 ++
 builtin-fetch.c             |  158 ++++++++++++++++++++++++++++++++++++++-----
 builtin-remote.c            |   86 +++++++----------------
 remote.c                    |    3 +-
 t/t5514-fetch-all.sh        |   76 +++++++++++++++++++++
 5 files changed, 249 insertions(+), 79 deletions(-)
 create mode 100755 t/t5514-fetch-all.sh

                 reply	other threads:[~2009-11-08 15:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4AF6E774.80909@gmail.com \
    --to=bgustavsson@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).