From: Sascha Silbe <x-yo17@se-silbe.de>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
poky@yoctoproject.org
Subject: Re: [PATCH] gitignore: ignore documentation build products
Date: Fri, 15 Dec 2017 15:15:49 +0100 [thread overview]
Message-ID: <toeefnwcc16.fsf@twin.sascha.silbe.org> (raw)
In-Reply-To: <f02f7dfd-cee9-809e-1ea3-313d1c42e79c@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]
Dear Alexander,
Alexander Kanavin <alexander.kanavin@linux.intel.com> writes:
> On 12/15/2017 12:52 PM, Sascha Silbe wrote:
>
>> +/documentation/bsp-guide/bsp-guide.html
>> +/documentation/bsp-guide/bsp-guide.pdf
>> +/documentation/bsp-guide/bsp-guide.tgz
>> +/documentation/dev-manual/dev-manual.html
>> +/documentation/dev-manual/dev-manual.pdf
>> +/documentation/dev-manual/dev-manual.tgz
>
> You can condense these into much fewer amount of entries using *, I think?
I've thought about that but e.g. /documentation/*/*.html would risk
excluding future manually edited files as well, not just the build
output. If source and build directory were different that would be much
less of a concern but the documentation doesn't use a separate build
directory. And unfortunately git only supports fnmatch() style patterns
in .gitignore, not bash-style brace expansion or regular expressions.
But if you're certain there won't be manually edited HTML or PDF files
in the future and would prefer a more compact solution I'm happy to
switch to using wildcards.
Sascha
--
Softwareentwicklung Sascha Silbe, Niederhofenstraße 5/1, 71229 Leonberg
https://se-silbe.de/
USt-IdNr.: DE281696641
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2017-12-15 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 10:52 [PATCH] gitignore: ignore documentation build products Sascha Silbe
2017-12-15 12:52 ` Alexander Kanavin
2017-12-15 14:15 ` Sascha Silbe [this message]
2017-12-15 14:39 ` Alexander Kanavin
2017-12-15 19:16 ` [PATCH v2] " Sascha Silbe
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=toeefnwcc16.fsf@twin.sascha.silbe.org \
--to=x-yo17@se-silbe.de \
--cc=alexander.kanavin@linux.intel.com \
--cc=poky@yoctoproject.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.