From: Hans Ulrich Niedermann <hun@n-dimensional.de>
To: grub-devel@gnu.org
Subject: Re: [MULTIBOOT2 SPEC PATCH v3 2/4] multiboot2: Use .gitignore files
Date: Wed, 13 May 2020 22:55:10 +0200 [thread overview]
Message-ID: <20200513225510.169ff545@n-dimensional.de> (raw)
In-Reply-To: <20200513162111.dzvtob4jpsvk2tdu@tomti.i.net-space.pl>
On Wed, 13 May 2020 18:21:11 +0200
Daniel Kiper <dkiper@net-space.pl> wrote:
> On Fri, May 08, 2020 at 06:50:47AM +0200, Hans Ulrich Niedermann
> wrote:
[... lots of gitignore stuff again ... ]
> > +/doc/mdate-sh
> > +/doc/texinfo.tex
> > +/install-sh
> > +/INSTALL
> > +/missing
> > +
> > +# Generated by "configure"
> > +Makefile
> > +.deps/
>
> Slash, "/", prefix?
Trailing slash just means "match directory" as opposed to "match file
or directory", so ".deps/" matches every directory named ".deps", while
the ".deps" pattern also matches files called ".deps". I'd rather such
a file showed up in "git status" so such a weird thing would be noticed.
The leading slash to match only relative to the .gitignore file's
directory is only implied with slashes somewhere within the pattern,
e.g. "doc/texinfo.tex" and "/doc/textinfo.tex" have the identical
meaning.
> > +
> > +/config.h
> > +/config.log
> > +/config.status
> > +/stamp-h1
> > +
> > +# Generated by "make"
> > +/doc/*.c.texi
> > +/doc/*.h.texi
> > +/doc/*.S.texi
> > +/doc/multiboot.info*
> > +/doc/stamp-vti
> > +/doc/version.texi
> > +
> > +*.o
>
> Could you be more consistent and list prefixed and not prefixed
> variants in the same order in each section?
Good point.
Uli
next prev parent reply other threads:[~2020-05-13 20:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 4:50 [MULTIBOOT2 SPEC PATCH v3 0/4] multiboot2: Clean up the example kernel Hans Ulrich Niedermann
2020-05-08 4:50 ` [MULTIBOOT2 SPEC PATCH v3 1/4] multiboot2: Allow autogen.sh to run with current gnulib Hans Ulrich Niedermann
2020-05-13 16:10 ` Daniel Kiper
2020-05-08 4:50 ` [MULTIBOOT2 SPEC PATCH v3 2/4] multiboot2: Use .gitignore files Hans Ulrich Niedermann
2020-05-13 16:21 ` Daniel Kiper
2020-05-13 20:55 ` Hans Ulrich Niedermann [this message]
2020-05-13 21:11 ` Hans Ulrich Niedermann
2020-05-14 5:49 ` Hans Ulrich Niedermann
2020-05-08 4:50 ` [MULTIBOOT2 SPEC PATCH v3 3/4] multiboot2: Make example kernel build at least for i386 Hans Ulrich Niedermann
2020-05-13 16:24 ` Daniel Kiper
2020-05-14 5:26 ` Hans Ulrich Niedermann
2020-05-08 4:50 ` [MULTIBOOT2 SPEC PATCH v3 4/4] multiboot2: fix example kernel header tag alignment Hans Ulrich Niedermann
2020-05-13 16:34 ` Daniel Kiper
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=20200513225510.169ff545@n-dimensional.de \
--to=hun@n-dimensional.de \
--cc=grub-devel@gnu.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.