From: Denton Liu <liu.denton@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] format-patch: make format.outputDirectory relative to worktree
Date: Tue, 24 Dec 2019 17:05:44 -0500 [thread overview]
Message-ID: <20191224220544.GA1917@generichostname> (raw)
In-Reply-To: <xmqq36d95xwh.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Tue, Dec 24, 2019 at 11:25:18AM -0800, Junio C Hamano wrote:
> Denton Liu <liu.denton@gmail.com> writes:
> > Rewrite the output directory logic for format-patch so that it will be
> > relative to the worktree of the directory. An escape hatch is provided
> > for if the previous behaviour is desired by prepending "./" to the
> > variable.
>
> Anything that forces existing users to change their existing
> settings is not an escape hatch. It merely is a regression with a
> possible workaround.
>
> So I dunno. I probably would have accepted a patch that *adds*
> outputDirectory configuration that behaves the way you are proposing
> in this patch if we did not have the variable yet in the system
> (i.e. three or four years ago), but I am not sure if it is a good
> idea to change it after these years.
Perhaps instead of switching the default behaviour so that it's always
relative to the top of the worktree, we can add some sort of prefix to
indicate that we want this behaviour. Maybe `worktree:path/from/top` or
`^path/from/top` or something like this?
Thanks,
Denton
next prev parent reply other threads:[~2019-12-24 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 12:37 [PATCH] format-patch: make format.outputDirectory relative to worktree Denton Liu
2019-12-24 19:25 ` Junio C Hamano
2019-12-24 22:05 ` Denton Liu [this message]
2019-12-25 2:26 ` 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=20191224220544.GA1917@generichostname \
--to=liu.denton@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox