From: Junio C Hamano <gitster@pobox.com>
To: "Alex Galvin via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Alex Galvin <agalvin@comqi.com>,
Alex Galvin <alex.v.galvin@gmail.com>
Subject: Re: [PATCH] git-svn: mention `svn:globalignores` in help+docs
Date: Tue, 13 Aug 2024 10:36:16 -0700 [thread overview]
Message-ID: <xmqq4j7o5nqn.fsf@gitster.g> (raw)
In-Reply-To: <pull.1766.git.git.1723500383989.gitgitgadget@gmail.com> (Alex Galvin via GitGitGadget's message of "Mon, 12 Aug 2024 22:06:23 +0000")
"Alex Galvin via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: Alex Galvin <alex.v.galvin@gmail.com>
>
> Git-SVN was previously taught to use the svn:globalignores attribute
> as well as svn:ignore when creating or showing .gitignore files from
> a Subversion repository. However, the documentation and help message
> still only mentioned svn:ignore. This commit updates Git-SVN's
> documentation and help command to mention the newly supported attribute.
Thanks for tying these loose ends. Very much appreciated.
> @@ -219,7 +219,7 @@ my %cmd = (
> "Set an SVN repository to a git tree-ish",
> { 'stdin' => \$_stdin, %cmt_opts, %fc_opts, } ],
> 'create-ignore' => [ \&cmd_create_ignore,
> - 'Create a .gitignore per svn:ignore',
> + 'Create a .gitignore per directory with svn:ignore and svn:globalignores',
I do not know how likely it is that Subversion gains even more
sources of exclusion data in the future, but it makes me wonder if a
phrase like "Create a .gitignore file from ignore properties of svn"
so that we do not have to muck with the message. Presumably those
who do use this feature know which properties Subversion uses to
record the ignored paths. On the other hand, if it is not expected
to happen very soon, I think the text in this patch is good enough,
and we can revisit the issue of help text getting overly long when
we do need to add the third one.
The same comment applies to the runtime option help for the other
one. I think listing the set of ignore properties we are aware of,
iow what you have in this patch, is perfectly appropriate for the
documentation.
Thanks.
next prev parent reply other threads:[~2024-08-13 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 22:06 [PATCH] git-svn: mention `svn:globalignores` in help+docs Alex Galvin via GitGitGadget
2024-08-13 17:36 ` Junio C Hamano [this message]
2024-08-13 19:05 ` Alex Galvin
2024-08-13 19:55 ` [PATCH v2] git-svn: mention `svn:global-ignores` " Alex Galvin via GitGitGadget
2024-08-13 22:33 ` Junio C Hamano
2024-08-14 17:53 ` Alex Galvin
2024-08-14 18:55 ` Junio C Hamano
2024-08-14 20:03 ` [PATCH v3] " Alex Galvin via GitGitGadget
2024-08-14 22:12 ` 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=xmqq4j7o5nqn.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=agalvin@comqi.com \
--cc=alex.v.galvin@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.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).