From: "Björn Gustavsson" <bgustavsson@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/8] Fetch improvements and re-implementation of remote update
Date: Tue, 10 Nov 2009 09:13:04 +0100 [thread overview]
Message-ID: <4AF92090.7030102@gmail.com> (raw)
To avoid having a commit where 'git remote update --prune' is broken
(except for cleanliness reasons, it would cause problems if someone
wants to bisect a breakage in that functionality), I have made
a slight change to one of Jay's patches and put my patch that
re-implements 'git remote update' last in the series.
Following this email, there will be series of patches starting
with number 5 and ending in number 8.
It can be applied directly on top of my fourth patch I sent out
yesterday ("Add missing test for 'git remote update --prune'").
The fifth patch in that series should be discarded.
Björn Gustavsson (1):
Re-implement 'git remote update' using 'git fetch'
Jay Soffian (3):
teach warn_dangling_symref to take a FILE argument
builtin-fetch: add --prune option
builtin-fetch: add --dry-run option
Documentation/fetch-options.txt | 9 ++++
builtin-fetch.c | 42 ++++++++++++++++--
builtin-remote.c | 90 ++++++++++++--------------------------
refs.c | 7 ++-
refs.h | 2 +-
5 files changed, 81 insertions(+), 69 deletions(-)
reply other threads:[~2009-11-10 8:13 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=4AF92090.7030102@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).