From: Jay Soffian <jaysoffian@gmail.com>
To: git@vger.kernel.org
Cc: "Jay Soffian" <jaysoffian@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Björn Gustavsson" <bgustavsson@gmail.com>
Subject: [PATCH 0/4] Teach fetch --prune and --dry run options
Date: Tue, 10 Nov 2009 00:03:30 -0500 [thread overview]
Message-ID: <1257829414-52316-1-git-send-email-jaysoffian@gmail.com> (raw)
(Darn it, I left the SOB off. This is a resend of the series with SOB. Sorry
for the noise...)
This series builds on bg/fetch-multi, by teaching fetch --prune, re-enabling
"remote update --prune" and ensuring its corresponding test now passes.
As a convenience to users used to "remote prune" supporting the "--dry-run"
option, we also teach this option to fetch since it's trivial to do so.
I've left out re-implementing "remote prune" as a synonym for "update --prune"
since it's not a 1:1 match. And as per Junio's comments, teaching fetch a
"--prune-only" option would be a UI wart.
Jay Soffian (4):
remote: refactor some logic into get_stale_heads()
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 | 38 +++++++++++------------------------
refs.c | 7 +++--
refs.h | 2 +-
remote.c | 40 +++++++++++++++++++++++++++++++++++++
remote.h | 3 ++
t/t5505-remote.sh | 2 +-
8 files changed, 108 insertions(+), 35 deletions(-)
next reply other threads:[~2009-11-10 5:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 5:03 Jay Soffian [this message]
2009-11-10 5:03 ` [PATCH 1/4] remote: refactor some logic into get_stale_heads() Jay Soffian
2009-11-10 5:03 ` [PATCH 2/4] teach warn_dangling_symref to take a FILE argument Jay Soffian
2009-11-10 5:03 ` [PATCH 3/4] builtin-fetch: add --prune option Jay Soffian
2009-11-10 5:03 ` [PATCH 4/4] builtin-fetch: add --dry-run option Jay Soffian
-- strict thread matches above, loose matches on Subject: below --
2009-11-10 4:58 [PATCH 0/4] Teach fetch --prune and --dry run options Jay Soffian
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=1257829414-52316-1-git-send-email-jaysoffian@gmail.com \
--to=jaysoffian@gmail.com \
--cc=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).