From: Jens Lehmann <Jens.Lehmann@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: [PATCH v2 0/2] Teach read-tree the -n|--dry-run option
Date: Wed, 25 May 2011 22:06:54 +0200 [thread overview]
Message-ID: <4DDD615E.7020809@web.de> (raw)
In-Reply-To: <7v39k37kmo.fsf@alter.siamese.dyndns.org>
Am 25.05.2011 01:18, schrieb Junio C Hamano:
> Jens Lehmann <Jens.Lehmann@web.de> writes:
>> My "Teach read-tree the -n|--dry-run option" adapted to this new flag
>> runs all tests successfully ...
>>
>>
>> unpack-trees.c | 4 ++--
>> unpack-trees.h | 3 ++-
>> 2 files changed, 4 insertions(+), 3 deletions(-)
>
> But on which change does this come?
As a preparing step for "read-tree the -n|--dry-run" (and adding
a dry-run option to other users of unpack_trees() should be pretty
straightforward now too).
The first patch in this series enables unpack_trees() to do a dry-run.
That enables users of unpack_trees() to see if running this function
with the update flag set would succeed.
The second patch uses this new dry_run flag to teach read-tree the
-n|--dry-run option.
Jens Lehmann (2):
unpack-trees: add the dry_run flag to unpack_trees_options
Teach read-tree the -n|--dry-run option
Documentation/git-read-tree.txt | 5 ++
builtin/read-tree.c | 3 +-
t/lib-read-tree.sh | 43 ++++++++++++++++++
t/t1000-read-tree-m-3way.sh | 81 +++++++++++++++++-----------------
t/t1001-read-tree-m-2way.sh | 45 ++++++++++---------
t/t1002-read-tree-m-u-2way.sh | 81 +++++++++++++++++-----------------
t/t1004-read-tree-m-u-wf.sh | 23 +++++-----
t/t1005-read-tree-reset.sh | 13 +++---
t/t1008-read-tree-overlay.sh | 3 +-
t/t1011-read-tree-sparse-checkout.sh | 27 ++++++-----
t/t1012-read-tree-df.sh | 9 ++--
t/t1020-subdirectory.sh | 5 +-
unpack-trees.c | 4 +-
unpack-trees.h | 3 +-
14 files changed, 202 insertions(+), 143 deletions(-)
create mode 100644 t/lib-read-tree.sh
--
1.7.5.2.355.gdceb0
next prev parent reply other threads:[~2011-05-25 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 21:07 [RFC PATCH] unpack-trees: add the dry_run flag to unpack_trees_options Jens Lehmann
2011-05-24 23:18 ` Junio C Hamano
2011-05-25 20:06 ` Jens Lehmann [this message]
2011-05-25 20:07 ` [PATCH v2 1/2] " Jens Lehmann
2011-05-25 21:36 ` Junio C Hamano
2011-05-25 20:10 ` [PATCH v2 2/2] Teach read-tree the -n|--dry-run option Jens Lehmann
2011-05-25 22:30 ` 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=4DDD615E.7020809@web.de \
--to=jens.lehmann@web.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.