git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Bruce Korb <bruce.korb@gmail.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>, git@vger.kernel.org
Subject: Re: How do I .gitignore files starting with "#"?
Date: Fri, 10 Sep 2010 21:41:29 +0200	[thread overview]
Message-ID: <201009102141.30416.jnareb@gmail.com> (raw)
In-Reply-To: <AANLkTi=D2M-QrbLodunphy+KJYt7eyfWsgzbwcBSZNyS@mail.gmail.com>

Bruce Korb wrote:
> On Fri, Sep 10, 2010 at 11:59 AM, Ævar Arnfjörð Bjarmason
> <avarab@gmail.com> wrote:
>> On Fri, Sep 10, 2010 at 18:52, Jakub Narebski <jnareb@gmail.com> wrote:
>>> Bruce Korb <bruce.korb@gmail.com> writes:
>>>
>>>> After trying lots of variations, I found it to be:
>>>>
>>>> \#*
>>>>
>>>> Not obvious and not easy to look up.  Please add it to your
>>>> .git/info/exclude sample text.  Thanks!
>>>
>>> Well, it is quite obvious to me, as escaping special characters using
>>> backslash is typical in Unix tools.
> 
> Like cscope, for example?
> 
>   "#what ever"
> 
> Others use:
> 
>    ./#whatever

Actually "/#whatever" would also work, but it would have different meaning,
anchoring filename so only files in given directory matches.

> 
> /etc/fstab requires \octal escapes, and not \xFF.

They are not escapes, but quoting of metacharacters (special characters).

> 
> There are many unix standards to choose from, hence my suggestion. :)
> That backslashes are sometimes used meant I found it before  pressing
> "send".

:-)

-- 
Jakub Narebski
Poland

  reply	other threads:[~2010-09-10 19:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10 16:59 How do I .gitignore files starting with "#"? Bruce Korb
2010-09-10 18:52 ` Jakub Narebski
2010-09-10 18:59   ` Ævar Arnfjörð Bjarmason
2010-09-10 19:11     ` Bruce Korb
2010-09-10 19:41       ` Jakub Narebski [this message]
2010-09-10 19:33     ` Jakub Narebski
2010-09-10 19:56       ` Jakub Narebski
2010-09-10 20:52         ` Bruce Korb

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=201009102141.30416.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=avarab@gmail.com \
    --cc=bruce.korb@gmail.com \
    --cc=git@vger.kernel.org \
    /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).