From: Junio C Hamano <gitster@pobox•com>
To: Joey Hess <id@joeyh•name>
Cc: Michael J Gruber <git@drmicha•warpmail.net>, git@vger•kernel.org
Subject: Re: [PATCH 2/4] add smudge-to-file and clean-from-file filter configuration
Date: Fri, 17 Jun 2016 10:29:26 -0700 [thread overview]
Message-ID: <xmqqk2hn207d.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <xmqq60t73igm.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Fri, 17 Jun 2016 09:09:45 -0700")
Junio C Hamano <gitster@pobox•com> writes:
> I wonder if we prefer not to make this customizable (i.e. not having
> to use'%p'). Unlike '%f' that is optional, smudgeTo and cleanFrom
> "filters" are not filters and MUST read from the path given and not
> from any other paths.
> ...
> Would an interface that always appends the pathname at the end of
> the command line string work?
Just to avoid misunderstanding, when I say "I wonder if we want to
go this route instead", I am open to a response that says "No, we do
not; going that route is worse because ...". Please do not take it
as a suggestion or request to "do it this way instead".
I may not even favor that other "route" I mention in my message with
"I wonder"; I am merely saying that I cannot come up with that
"because ..." part to reject it myself, and asking for help from
others.
In this case, I would be happy to hear "Yes, '%p' may merely be a
way to allow taking the pathname at anywhere on the command line,
but that flexibility is important because...".
Thanks.
next prev parent reply other threads:[~2016-06-17 17:29 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
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 [this message]
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=xmqqk2hn207d.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
--cc=id@joeyh$(echo .)name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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