From: Johannes Sixt <j.sixt@viscovery.net>
To: Kevin Ballard <kevin@sb.org>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
git@vger.kernel.org, "Marc Strapetz" <marc.strapetz@syntevo.com>
Subject: Re: [PATCH] attr: support quoting pathname patterns in C style
Date: Tue, 09 Nov 2010 08:48:16 +0100 [thread overview]
Message-ID: <4CD8FCC0.2030500@viscovery.net> (raw)
In-Reply-To: <626BD1B6-4DDF-457F-B430-F15C891710E2@sb.org>
Am 11/8/2010 22:56, schrieb Kevin Ballard:
> Basically what I'm trying to say is, we already break one particular
> "rather rare" setup. I would love to come up with a solution that supports
> both setups, but I don't know if one exists outside of using a config
> variable to control whether git attribute patterns support quoting (a solution
> I am not particularly fond of for this case).
Can we perhaps have a pseudo-attribute 'quoted-names' that is to be used
like this:
* quoted-names
"file 1" binary
file.1 -diff
Its meaning would be that the remainder of the current .gitattributes file
is to be parsed with C style path quoting enabled. The glob given with
this attribute is irrelevant and ignored.
I didn't check whether old gits would ignore this unknown attribute.
-- Hannes
next prev parent reply other threads:[~2010-11-09 7:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 12:24 .gitattributes escape character? Marc Strapetz
2010-11-03 15:47 ` Nguyen Thai Ngoc Duy
2010-11-03 17:13 ` Marc Strapetz
2010-11-03 21:03 ` Kevin Ballard
2010-11-04 13:55 ` [PATCH] attr: support quoting pathname patterns in C style Nguyễn Thái Ngọc Duy
2010-11-04 17:21 ` Sverre Rabbelier
2010-11-04 22:53 ` Eric Sunshine
2010-11-05 2:02 ` Nguyen Thai Ngoc Duy
2010-11-05 16:58 ` Junio C Hamano
2010-11-05 21:46 ` Kevin Ballard
2010-11-08 18:40 ` Junio C Hamano
2010-11-08 21:56 ` Kevin Ballard
2010-11-09 7:48 ` Johannes Sixt [this message]
2010-11-09 8:08 ` Kevin Ballard
2010-11-10 0:07 ` Junio C Hamano
2010-11-10 0:27 ` Kevin Ballard
2010-11-06 8:28 ` Marc Strapetz
2010-11-07 8:05 ` Nguyễn Thái Ngọc Duy
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=4CD8FCC0.2030500@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kevin@sb.org \
--cc=marc.strapetz@syntevo.com \
--cc=pclouds@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).