qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] .gitignore: include common build sub-directories
Date: Mon, 13 Apr 2020 22:32:00 +0100	[thread overview]
Message-ID: <87imi38433.fsf@linaro.org> (raw)
In-Reply-To: <2c489489-f459-f029-029e-74bfbfc70e49@redhat.com>


Eric Blake <eblake@redhat.com> writes:

> On 4/13/20 11:29 AM, Alex Bennée wrote:
>> As out-of-tree builds become more common (or rather building in a
>> subdir) we can add a lot of load to "git ls-files" as it hunts down
>> sub-directories that are irrelevant to the source tree. This is
>> especially annoying if you have a prompt that attempts to summarise
>> the current git status on command completion.
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> ---
>>   .gitignore | 2 ++
>>   1 file changed, 2 insertions(+)
>> diff --git a/.gitignore b/.gitignore
>> index 0c5af83aa74..7757dc08a08 100644
>> --- a/.gitignore
>> +++ b/.gitignore
>> @@ -141,6 +141,8 @@ cscope.*
>>   tags
>>   TAGS
>>   docker-src.*
>> +build
>> +builds
>
> Would 'build-*' be worth adding as well?

Sure - I'll add it to v2.

>
> The idea makes sense to me (as I've already done the same in my
> ./git/info/exclude locally),
> Reviewed-by: Eric Blake <eblake@redhat.com>


-- 
Alex Bennée


  reply	other threads:[~2020-04-13 21:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13 16:29 [PATCH] .gitignore: include common build sub-directories Alex Bennée
2020-04-13 18:26 ` Eric Blake
2020-04-13 21:32   ` Alex Bennée [this message]
2020-04-13 21:42     ` Eric Blake
2020-04-13 21:45       ` Philippe Mathieu-Daudé
2020-04-14  8:00       ` Markus Armbruster
2020-04-14  8:47         ` Alex Bennée
2020-04-14  9:53           ` Philippe Mathieu-Daudé
2020-04-14 15:06 ` Richard Henderson
2020-04-14 16:31   ` Alex Bennée
2020-04-14 16:39     ` Richard Henderson

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=87imi38433.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=eblake@redhat.com \
    --cc=qemu-devel@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).