From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Bruce Korb" <bruce.korb@gmail.com>,
git@vger.kernel.org, "Andreas Schwab" <schwab@linux-m68k.org>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [PATCH] Document escaping of special characters in gitignore files
Date: Wed, 5 Jan 2011 22:02:32 +0100 [thread overview]
Message-ID: <201101052202.34043.jnareb@gmail.com> (raw)
In-Reply-To: <7vk4ijccji.fsf@alter.siamese.dyndns.org>
On Wed, 5 Jan 2011, Junio C Hamano wrote:
> Perhaps a single liner comment to describe the three examples immediately
> below "exclude patterns (uncomment them..." is in order in that case,
> something like:
>
> # exclude patterns (object and library, emacs backup, emacs autosave
> # files) -- uncomment if you want to use them
> # *.[oa]
> # *~
Errr... I think that '*~' pattern is generic UNIX backup, like '*.bak'
is for MS-DOS / MS Windows.
http://en.wikipedia.org/wiki/Tilde#Backup_filenames
Backup filenames
The dominant Unix convention for naming backup copies of files is
appending a tilde to the original file name. It originated with the
Emacs text editor[citation needed] and was adopted by many other
editors and some command-line tools.
> # \#*#
Anyway, should I reroll this patch with above addition? Should I add
an explanation why we can use `\#` but need to use "{tilde}#"?
--
Jakub Narebski
Poland
prev parent reply other threads:[~2011-01-05 21:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 13:38 [PATCH] Document escaping of special characters in gitignore files Jakub Narebski
2011-01-05 15:53 ` Andreas Schwab
2011-01-05 18:42 ` Junio C Hamano
2011-01-05 19:27 ` Jakub Narebski
2011-01-05 19:38 ` Thomas Rast
2011-01-05 20:12 ` Bruce Korb
2011-01-05 20:37 ` Junio C Hamano
2011-01-05 21:02 ` Jakub Narebski [this message]
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=201101052202.34043.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=avarab@gmail.com \
--cc=bruce.korb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=schwab@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.