From: Junio C Hamano <gitster@pobox.com>
To: Patrick Higgins <patrick.higgins@cexp.com>
Cc: git@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>
Subject: Re: [PATCH v3/RFC] Remove the use of '--' in merge program invocation
Date: Mon, 16 Jun 2008 17:05:25 -0700 [thread overview]
Message-ID: <7vlk157woq.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1213659221-27519-1-git-send-email-patrick.higgins@cexp.com> (Patrick Higgins's message of "Mon, 16 Jun 2008 17:33:41 -0600")
Patrick Higgins <patrick.higgins@cexp.com> writes:
> Put a "./" at the beginning of all paths given to the merge program so
> that filenames beginning with a '-' character don't get interpreted as
> options.
>
> This deals with a problem where kdiff3 can be compiled with or without
> support for the '--' separator between options and filenames.
>
> Signed-off-by: Patrick Higgins <patrick.higgins@cexp.com>
> ---
>
> This is applying Junio's idea because my earlier attempts would fail on files
> that started with a dash. This should work for those files with kdiff3
> compiled with or without '--' support, does not require any additional
> overhead to determine if kdiff3 has that support, and the technique should
> work for all merge programs in case any others have the problem kdiff3 has.
>
> My only concern is if 'git ls-files -u' ever returns absolute paths,
> then this will not work.
What do you mean by "absolute paths"? The path git proper deals with is
always relative to the root of the repository's work tree, so you won't be
seeing "/home/patrick/src/Makefile" from ls-files if that is what you are
worried about.
This change applies to all the backends not just kdiff3; people who use
different merge backends please give success (or breakage) reports.
Thanks.
next prev parent reply other threads:[~2008-06-17 0:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 23:33 [PATCH v3/RFC] Remove the use of '--' in merge program invocation Patrick Higgins
2008-06-17 0:05 ` Junio C Hamano [this message]
2008-06-17 16:52 ` Patrick.Higgins
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=7vlk157woq.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=patrick.higgins@cexp.com \
--cc=tytso@mit.edu \
/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).