From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: musl setup attempt
Date: Sat, 16 Mar 2013 18:58:25 -0400 [thread overview]
Message-ID: <20130316225824.GK20323@brightrain.aerifal.cx> (raw)
In-Reply-To: <20130315141141.1f14e6a4.idunham@lavabit.com>
On Fri, Mar 15, 2013 at 02:11:41PM -0700, Isaac Dunham wrote:
> On Fri, 15 Mar 2013 07:54:39 -0400
> LM <lmemsm@gmail.com> wrote:
>
> > I have really mixed results with reporting portability bugs. More
> > often than not, projects refuse to accept the bugs unless they're for
> > platforms they officially support. I typically work with
> > cross-platform software, but many of the cross-platform projects still
> > only officially support a limited number of systems. Some of them
> > have even been down-right nasty when I submit a patch to fix an issue
> > for my platform. (Of course, I've run across some projects where the
> > developers have been very nice too and fix things extremely quickly.)
> > Am very curious if anyone else has had problems with this sort of
> > thing and how you handle the situation.
>
> A few points:
> 1) Patches beat bug reports. Make sure that you note upstream policy
> about copyright assignments and so on, though.
> Also follow the code style upstream uses.
> 2) Make sure it's not going to break upstream policy.
> Examples: don't change -std=c89
> 3) Make sure it doesn't disable something for other platforms (eg,
> breaking tests for uclibc)
> 4) Make it as little change as appropriate
> 5) If at all possible, test on other platforms.
>
> The best response I had was a trivial patch for libnl (adding a
> couple headers) which I prepared, tested on musl and glibc, then
> sent with a comment that it fixed build on musl and worked on glibc.
> It was applied almost immediately.
Thank you. This email belongs on the wiki.
Rich
next prev parent reply other threads:[~2013-03-16 22:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 11:54 LM
2013-03-13 14:07 ` Isaac Dunham
2013-03-13 18:49 ` John Spencer
2013-03-15 11:54 ` LM
2013-03-15 21:11 ` Isaac Dunham
2013-03-16 13:36 ` LM
2013-03-16 22:58 ` Rich Felker [this message]
2013-03-14 11:02 LM
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=20130316225824.GK20323@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).