Re: git-archive and submodules
Robert Quattlebaum darco at deepdarc.com writes: I got too busy to continue working to get it included. Please feel free to pick up where I left off. On Apr 20, 2012, at 2:32 PM, André Caron andre.l.caron at gmail.com wrote: Since you've touched this only last year, I'd like to know where you were at and I can see if I can pick up where you left off (unless you want to finish yourself). Greetings I was just wondering whether there been any progress on this topic since last year... André ? Cheers Damien -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH] git-check-ref-format: fix typo in man page
--- Documentation/git-check-ref-format.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/git-check-ref-format.txt b/Documentation/git-check-ref-format.txt index 8611a99..377c85a 100644 --- a/Documentation/git-check-ref-format.txt +++ b/Documentation/git-check-ref-format.txt @@ -100,7 +100,7 @@ OPTIONS --normalize:: Normalize 'refname' by removing any leading slash (`/`) characters and collapsing runs of adjacent slashes between - name components into a single slash. Iff the normalized + name components into a single slash. If the normalized refname is valid then print it to standard output and exit with a status of 0. (`--print` is a deprecated way to spell `--normalize`.) -- 2.7.4
Re: [PATCH] git-check-ref-format: fix typo in man page
Thanks all for the feedback. On 2017-02-19 21:40, Philip Oakley wrote: > For those not familiar with 'iff', then a change to the doc is worthwhile. Exactly. Not being a native English speaker, I had never seen 'iff' used before. Now that you guys have pointed me to its meaning I guess it makes sense in this context. That being said, IMHO software documentation is not a mathematics textbook, and should be written in "plain" English, so On 2017-02-19 03:27, Jeff King wrote: > So maybe an overall improvement would be something like: > > If the normalized refname is valid then print it to standard output > and exit with a status of 0. Otherwise, exit with a non-zero status. I'll submit a revised patch shortly, following your suggestion. Cheers Damien
[PATCH v2] git-check-ref-format: clarify man for --normalize
Use of 'iff' may be confusing to people not familiar with this term. Improving the --normalize option's documentation to remove the use of 'iff', and clearly describe what happens when the condition is not met. --- Documentation/git-check-ref-format.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/git-check-ref-format.txt b/Documentation/git-check-ref-format.txt index 8611a99..92777ce 100644 --- a/Documentation/git-check-ref-format.txt +++ b/Documentation/git-check-ref-format.txt @@ -100,10 +100,10 @@ OPTIONS --normalize:: Normalize 'refname' by removing any leading slash (`/`) characters and collapsing runs of adjacent slashes between - name components into a single slash. Iff the normalized + name components into a single slash. If the normalized refname is valid then print it to standard output and exit - with a status of 0. (`--print` is a deprecated way to spell - `--normalize`.) + with a status of 0, otherwise exit with a non-zero status. + (`--print` is a deprecated way to spell `--normalize`.) EXAMPLES -- 2.7.4
