From: Joey Hess <id@joeyh.name>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/4] add smudge-to-file and clean-from-file filter configuration
Date: Fri, 17 Jun 2016 09:13:11 -0400 [thread overview]
Message-ID: <20160617131311.GC24025@kitenet.net> (raw)
In-Reply-To: <xmqqy4643ig1.fsf@gitster.mtv.corp.google.com>
Junio C Hamano wrote:
> There is what we would want to fix, though. "worktree file" should
> be spelled "working tree file". This used not to matter before "git
> worktree" was invented (before that we used these two terms
> interchangeably), but these days the distinction matters.
The existing documentation that I am patching uses the term "worktree
file" which is why I continued to use that wording.
(Unless this is a documentation transition that you want to happen
peicemeal as documentation is updated for other reasons?)
> > +filter.<driver>.clean-from-file::
>
> Documentation/config.txt hopefully lists all the configuration, but
> I do not see anything that uses 'words-joined-with-dash' format.
> Please do not invent new out-of-convention names.
Point taken; I'll use cleanFromFile and smudgeToFile.
Here's a revised version of the documentation that I think takes the other
suggestions onboard. I emphasise that clean and smudge operate as filters,
to contrast better with cleanFromFile and smudgeToFile not operating as
regular stdio filters.
filter.<driver>.clean::
- The command which is used to convert the content of a worktree
+ The command which is used as a filter to convert the content of a worktree
file to a blob upon checkin. See linkgit:gitattributes[5] for
details.
filter.<driver>.smudge::
- The command which is used to convert the content of a blob
+ The command which is used as a filter to convert the content of a blob
object to a worktree file upon checkout. See
linkgit:gitattributes[5] for details.
+filter.<driver>.cleanFromFile::
+ Similar to filter.<driver>.clean but the specified command
+ directly accesses a worktree file on disk, rather than
+ receiving the file content from standard input.
+ In the command, "%p" is replaced with the name of the file.
+ Only used when filter.<driver>.clean is also configured.
+ See linkgit:gitattributes[5] for details.
+
+filter.<driver>.smudgeToFile::
+ Similar to filter.<driver>.smudge but the specified command
+ writes the content of a blob directly to a worktree file,
+ rather than to standard output.
+ In the command, "%p" is replaced with the name of the file.
+ Only used when filter.<driver>.smudge is also configured.
+ See linkgit:gitattributes[5] for details.
+
This could be extended more, but I think this should describe the config
settings concisely and point to the more involved discussion of filter drivers
in gitattributes.
--
see shy jo
next prev parent reply other threads:[~2016-06-17 13:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 20:32 [PATCH 0/4] extend smudge/clean filters with direct file access Joey Hess
2016-06-16 20:32 ` [PATCH 1/4] clarify %f documentation Joey Hess
2016-06-16 21:33 ` Junio C Hamano
2016-06-17 2:48 ` Joey Hess
2016-06-17 3:25 ` Junio C Hamano
2016-06-17 12:32 ` Joey Hess
2016-06-17 15:57 ` Junio C Hamano
2016-06-16 20:32 ` [PATCH 2/4] add smudge-to-file and clean-from-file filter configuration Joey Hess
2016-06-16 21:57 ` Junio C Hamano
2016-06-17 13:13 ` Joey Hess [this message]
2016-06-17 18:26 ` Junio C Hamano
2016-06-17 6:05 ` Eric Sunshine
2016-06-17 9:36 ` Michael J Gruber
2016-06-17 12:47 ` Joey Hess
2016-06-17 16:09 ` Junio C Hamano
2016-06-17 17:29 ` Junio C Hamano
2016-06-17 17:37 ` Joey Hess
2016-06-17 18:06 ` Joey Hess
2016-06-17 18:24 ` Junio C Hamano
2016-06-16 20:32 ` [PATCH 3/4] use clean-from-file in git add Joey Hess
2016-06-16 20:32 ` [PATCH 4/4] use smudge-to-file in git checkout etc Joey Hess
2016-06-16 20:55 ` Joey Hess
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=20160617131311.GC24025@kitenet.net \
--to=id@joeyh.name \
--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.