From: Junio C Hamano <gitster@pobox.com>
To: Dmitry Ivankov <divanorama@gmail.com>
Cc: git@vger.kernel.org, Jonathan Nieder <jrnieder@gmail.com>,
Ramkumar Ramachandra <artagnon@gmail.com>,
Johan Herland <johan@herland.net>,
"Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [PATCH 2/3] doc/fast-import: document feature import-marks-if-exists
Date: Tue, 12 Jul 2011 10:00:46 -0700 [thread overview]
Message-ID: <7voc0z8mdd.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1310483428-29833-3-git-send-email-divanorama@gmail.com> (Dmitry Ivankov's message of "Tue, 12 Jul 2011 21:10:27 +0600")
Dmitry Ivankov <divanorama@gmail.com> writes:
> fast-import parameter --import-marks-if-exists was introduced in
> commit dded4.. --import-marks can be set via a "feature" command in
> a fast-import stream and --import-marks-if-exists has support for
> such specification too, for free.
>
> Document "feature import-marks-if-exists=<file>" command and add a
> minimalistic test for it.
>
> Signed-off-by: Dmitry Ivankov <divanorama@gmail.com>
Thanks.
> Documentation/git-fast-import.txt | 5 +++++
> t/t9300-fast-import.sh | 15 +++++++++++++++
> 2 files changed, 20 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/git-fast-import.txt b/Documentation/git-fast-import.txt
> index 3f5b912..bdcc81c 100644
> --- a/Documentation/git-fast-import.txt
> +++ b/Documentation/git-fast-import.txt
> @@ -1005,6 +1005,11 @@ import-marks::
> second, an --import-marks= command-line option overrides
> any "feature import-marks" command in the stream.
>
> +import-marks-if-exists::
> + Like import-marks but instead of erroring out, silently
> + skips the file if it does not exist. Differences from --
> + version are the same as with import-marks feature above.
Wouldn't it be more concise and complete to do it this way instead? It
avoids duplication and also clarifies you cannot mix these two.
diff --git a/Documentation/git-fast-import.txt b/Documentation/git-fast-import.txt
index 249249a..e939e74 100644
--- a/Documentation/git-fast-import.txt
+++ b/Documentation/git-fast-import.txt
@@ -995,10 +995,14 @@ force::
(see OPTIONS, above).
import-marks::
+import-marks-if-exists::
Like --import-marks except in two respects: first, only one
- "feature import-marks" command is allowed per stream;
+ "feature import-marks" command or "feature import-marks-if-exists"
+ is allowed per stream;
second, an --import-marks= command-line option overrides
- any "feature import-marks" command in the stream.
+ any "feature import-marks" command in the stream. Similarly,
+ import-marks-if-exists corresponds to --import-marks-if-exists
+ from the command line.
cat-blob::
ls::
>
> +test_expect_success 'R: feature import-marks-if-exists' '
> + rm -f io.marks &&
> + blob=$(echo hi | git hash-object --stdin) &&
> + echo ":1 $blob" >expect &&
> + git fast-import --import-marks-if-exists=io.marks --export-marks=io.marks <<-\EOF &&
> + feature import-marks-if-exists=io.marks
> + blob
> + mark :1
> + data 3
> + hi
> +
> + EOF
> + test_cmp expect io.marks
> +'
Do you really want both the command line option and feature in this test?
There are at least four cases [*1*] you would want to test (a part of
blame lies in the original test you copied this from).
- "if exists" should not fail if the marks file does not exist;
- "if exists" reads marks if exists (not tested in this patch);
- having "feature import-marks-if-exists" will trigger this feature
without command line option (not tested in this patch); and
- having "feature import-marks-if-exists" will be overridden by
the command line option (not tested in this patch).
[Footnote]
*1* Ideally, the test should also cover these 16 combinations:
io.marks file (2 cases: exists or missing)
times
--import-mark-if-exists (2 cases: exists or missing)
times
feature import-marks-if-exists (4 cases: missing,
same as command line,
different from command line,
given more than one)
next prev parent reply other threads:[~2011-07-12 17:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 15:10 [PATCH 0/3] doc/{fast-import,remote-helpers}: few clarifications Dmitry Ivankov
2011-07-12 15:10 ` [PATCH 1/3] doc/fast-import: clarify notemodify command Dmitry Ivankov
2011-07-12 15:10 ` [PATCH 2/3] doc/fast-import: document feature import-marks-if-exists Dmitry Ivankov
2011-07-12 17:00 ` Junio C Hamano [this message]
2011-07-13 10:27 ` Ramkumar Ramachandra
2011-07-12 15:10 ` [PATCH 3/3] doc/remote-helpers: document the gitdir feature Dmitry Ivankov
2011-07-13 12:04 ` Sverre Rabbelier
2011-07-13 17:10 ` [PATCH v2 1/3] doc/fast-import: clarify notemodify command Dmitry Ivankov
2011-07-22 19:32 ` Johan Herland
2011-07-13 17:10 ` [PATCH v2 2/3] doc/fast-import: document feature import-marks-if-exists Dmitry Ivankov
2011-07-13 17:10 ` [PATCH v2 3/3] remote-helpers: export GIT_DIR variable to helpers Dmitry Ivankov
2011-07-13 17:14 ` Dmitry Ivankov
2011-07-13 17:36 ` Sverre Rabbelier
2011-07-13 18:10 ` Dmitry Ivankov
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7voc0z8mdd.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=artagnon@gmail.com \
--cc=divanorama@gmail.com \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
--cc=jrnieder@gmail.com \
--cc=spearce@spearce.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).