From: Thomas Huth <thuth@redhat.com>
To: Eric Blake <eblake@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-trivial@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH] Simplify the .gitignore file
Date: Wed, 9 Sep 2020 09:58:56 +0200 [thread overview]
Message-ID: <dfa64d8f-6625-957e-71ab-41a569ea9819@redhat.com> (raw)
In-Reply-To: <2f1b8cb5-6639-a530-1467-28fb6a89c926@redhat.com>
On 08/09/2020 14.50, Eric Blake wrote:
> On 9/7/20 12:42 PM, Thomas Huth wrote:
>> Now that we always do out-of-tree builds (and the in-tree builds are
>> faked via a "build" directory), we can simplify out .gitignore file
>
> s/out/our/
>
>> quite a bit.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> .gitignore | 158 -----------------------------------------------------
>> 1 file changed, 158 deletions(-)
>>
>
> I like the idea. As Phillipe pointed out, there are still a few files
> that may be created by merely running './configure' or common editor
> droppings or workflow setups that are still worth ignoring, but as most
> of these truly no longer appear during a fresh checkout, it makes sense
> to clean it up.
>
> Someone who still wants to use 'fake in-tree' builds and creates
> symlinks for themselves will no longer have those symlinks ignored by
> this pruned file, but can edit their own .git/info/exclude file to match
> their preferences.
>
>> diff --git a/.gitignore b/.gitignore
>> index 4ccb9ed975..bb916594eb 100644
>> --- a/.gitignore
>> +++ b/.gitignore
>> @@ -1,165 +1,7 @@
>> /GNUmakefile
>> /build/
>
> Our 'fake in-tree' build uses just 'build', but ignoring '/build*/'
> might be wiser to automatically ignore all other variations on the theme
> of a subdirectory per build.
At least I am doing my out-of-tree builds completely outside of the
source tree. I think if someone wants to use directories within the
source tree for this, they can also simply add them to their private
.gitignore / .git/info/exclude file instead, then you're also more
flexible with the naming.
Thomas
prev parent reply other threads:[~2020-09-09 7:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 17:42 [PATCH] Simplify the .gitignore file Thomas Huth
2020-09-07 19:43 ` Philippe Mathieu-Daudé
2020-09-08 14:41 ` Thomas Huth
2020-09-08 14:50 ` Thomas Huth
2020-09-08 16:04 ` Philippe Mathieu-Daudé
2020-09-09 7:24 ` Markus Armbruster
2020-09-08 12:50 ` Eric Blake
2020-09-09 7:58 ` Thomas Huth [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=dfa64d8f-6625-957e-71ab-41a569ea9819@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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).