From: "Jan Beulich" <JBeulich@suse.com>
To: "Bryce McKinlay" <bmckinlay@gmail.com>
Cc: <java@gcc.gnu.org>
Subject: Re: libjava build failure with read-only source tree
Date: Thu, 29 Sep 2011 09:06:00 -0000 [thread overview]
Message-ID: <4E84512102000078000586D2@nat28.tlf.novell.com> (raw)
In-Reply-To: <CALUNu-okfMZY9h8kTg0s5NXDg_T28-76prCGt5UaTQjpi5AQ6g@mail.gmail.com>
>>> On 29.09.11 at 10:39, Bryce McKinlay <bmckinlay@gmail.com> wrote:
> On Thu, Sep 29, 2011 at 9:18 AM, Jan Beulich <JBeulich@suse.com> wrote:
>
>> As this isn't the first time I encounter this in the libjava subtree, can it
>> be made a requirement for testing changes that they must work with
>> fully read-only source trees? And/or if there's some sort of automatic
>> testing in place, could that be adjusted to include a respective check?
>
> It would be heavy-handed to require every contributor to test patches
> with a read-only tree. We don't want to make the patch submission
> process any more onerous than it already is.
I certainly realize that. But this wouldn't be needed for all submissions,
just such that alter the tree layout of the build tree.
Btw., the patch that I had embedded in the original mail works, but as
there's no maintainer listed for libjava in ./MAINTAINERS I'm entirely
unclear who I would need to turn to in order to get approval to commit
this.
Jan
next prev parent reply other threads:[~2011-09-29 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 8:18 Jan Beulich
2011-09-29 8:40 ` Bryce McKinlay
2011-09-29 9:06 ` Jan Beulich [this message]
2011-09-29 9:32 ` Bryce McKinlay
2011-09-29 9:34 ` Andrew Haley
2011-09-29 9:48 ` 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=4E84512102000078000586D2@nat28.tlf.novell.com \
--to=jbeulich@suse.com \
--cc=bmckinlay@gmail.com \
--cc=java@gcc.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).