From: Jan Beulich <jbeulich@suse.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>, Wei Liu <wl@xen.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xenproject.org,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
Doug Goldstein <cardoe@cardoe.com>
Subject: Re: [Xen-devel] [XEN PATCH 3/8] xen: Update Kconfig to Linux v5.4
Date: Mon, 16 Dec 2019 16:55:52 +0100 [thread overview]
Message-ID: <4b4a6d47-0181-fac3-7a48-5cfbc85ee575@suse.com> (raw)
In-Reply-To: <20191216135658.GA1267@perard.uk.xensource.com>
On 16.12.2019 15:01, Anthony PERARD wrote:
> On Mon, Dec 16, 2019 at 11:16:52AM +0100, Jan Beulich wrote:
>> What headers are you taking about? My question was about the placement
>> of .gitignore entries only. I'm pretty sure I had previously expressed
>> that I'm not overly happy to see needless scattering around of them.
>> I'm merely trying to understand if here we have a case of "needless".
>>
>>> I find your lack of consistency in review requests impossible to predict.
>>
>> What consistency? What's wrong with putting the two lines in the top
>> level .gitignore, or keeping them where they are? I anyway doubt
>> there's a need to keep our .gitignore in sync with Linux'es.
>
> I think scattering the .gitignore around make them easier to manage,
> especially when entries aren't useful anymore. Otherwise, we end up
> with a .gitignore at the root with entries that aren't needed anymore
> because they can be hard to figure out if they are useful or not.
> Or, when globing is involve, we could end-up ignoring files that
> shouldn't.
Right, especially this last point makes scattering entries have some
value. But then let's truly scatter them, not accumulate all sorts
of stuff in xen/.gitignore.
> I'm planning to import more of Kbuild, which Makefile.host comes from,
> to build only the hypervisor, so there's going to be other artefact that
> will be generated only in xen/. So I've added those two new entries in
> xen/.gitignore in anticipation, and to avoid getting xen/tools/kconfig
> out-of-sync with Linux's one (Well I didn't know those two entries were
> there in the first place).
>
> I could add "/xen/**/*.tab.[ch]" in the root .gitignore if you prefer
> even though I don't like this approch.
But this then still is too wide a pattern, as per above. A
sufficiently specific one would be as good as one without path
in a .gitignore deep enough into the tree, if we wanted to go
the "truly scatter" route.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-12-16 15:55 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 18:27 [Xen-devel] [XEN PATCH 0/8] xen: Kconfig update with few extra Anthony PERARD
2019-12-12 18:27 ` [Xen-devel] [XEN PATCH 1/8] Config.mk: Remove unused setvar_dir macro Anthony PERARD
2019-12-12 18:30 ` Andrew Cooper
2019-12-13 14:51 ` Anthony PERARD
2019-12-12 18:27 ` [Xen-devel] [XEN PATCH 2/8] Config.mk: Remove stray comment Anthony PERARD
2019-12-12 18:32 ` Andrew Cooper
2019-12-13 15:16 ` Anthony PERARD
2019-12-12 18:27 ` [Xen-devel] [XEN PATCH 3/8] xen: Update Kconfig to Linux v5.4 Anthony PERARD
2019-12-12 18:45 ` Andrew Cooper
2019-12-13 15:31 ` Anthony PERARD
2019-12-13 11:05 ` Jan Beulich
2019-12-13 15:49 ` Anthony PERARD
2019-12-13 16:59 ` Jan Beulich
2019-12-13 19:17 ` Andrew Cooper
2019-12-16 10:16 ` Jan Beulich
2019-12-16 14:01 ` Anthony PERARD
2019-12-16 15:55 ` Jan Beulich [this message]
2019-12-16 16:34 ` Anthony PERARD
2019-12-12 18:27 ` [Xen-devel] [XEN PATCH 4/8] xen: Have Kconfig check $(CC)'s version Anthony PERARD
2019-12-12 18:56 ` Andrew Cooper
2019-12-13 16:08 ` Anthony PERARD
2019-12-12 18:27 ` [Xen-devel] [XEN PATCH 5/8] xen: Import cc-ifversion from Kbuild Anthony PERARD
2019-12-12 18:56 ` Andrew Cooper
2019-12-12 18:27 ` [Xen-devel] [XEN PATCH 6/8] xen: Move CONFIG_INDIRECT_THUNK to Kconfig Anthony PERARD
2019-12-12 18:58 ` Andrew Cooper
2019-12-13 11:13 ` Jan Beulich
2019-12-13 12:18 ` Anthony PERARD
2019-12-13 12:27 ` Jan Beulich
2020-02-18 16:43 ` Jan Beulich
2020-02-18 17:13 ` Anthony PERARD
2020-02-19 7:55 ` Jan Beulich
2019-12-12 18:27 ` [Xen-devel] [XEN PATCH 7/8] xen: Use $(CONFIG_CC_IS_CLANG) instead of $(clang) in Makefile Anthony PERARD
2019-12-12 19:00 ` Andrew Cooper
2019-12-13 14:37 ` Anthony PERARD
2019-12-12 18:27 ` [Xen-devel] [XEN PATCH 8/8] xen: Move GCC_HAS_VISIBILITY_ATTRIBUTE to Kconfig and common Anthony PERARD
2019-12-12 19:04 ` Andrew Cooper
2019-12-13 11:27 ` Jan Beulich
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=4b4a6d47-0181-fac3-7a48-5cfbc85ee575@suse.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=cardoe@cardoe.com \
--cc=ian.jackson@eu.citrix.com \
--cc=julien@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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.