From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/13794 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Contributing Date: Thu, 14 Feb 2019 18:17:53 -0500 Message-ID: <20190214231753.GW23599@brightrain.aerifal.cx> References: Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="56262"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.5.21 (2010-09-15) Cc: musl@lists.openwall.com To: Nick Bray Original-X-From: musl-return-13810-gllmg-musl=m.gmane.org@lists.openwall.com Fri Feb 15 00:18:09 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1guQGe-000EXa-Q9 for gllmg-musl@m.gmane.org; Fri, 15 Feb 2019 00:18:08 +0100 Original-Received: (qmail 11301 invoked by uid 550); 14 Feb 2019 23:18:06 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 11281 invoked from network); 14 Feb 2019 23:18:06 -0000 Content-Disposition: inline In-Reply-To: Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:13794 Archived-At: On Thu, Feb 14, 2019 at 01:50:46PM -0800, Nick Bray wrote: > I have a few small patches to Musl I'm interested in upstreaming. > What is the expected workflow? > > I assume the first step is "git send-email" to this list? git format-patch with attachment(s) is preferred. Commit messages should be formatted similar to other commits and should explain motivation and observable effects of change. > What happens next? Comments from maintainer (myself) and community via the list. If they're acceptable as-is, they're usually merged/pushed fairly quickly. This is usually the case for clear bug fixes, fixes for oversights of minor requirements, etc. If the patch is making major invasive changes, adding new functionality, etc., though, there will usually be more discussion and a need for motivation/justification. > Is there a canonical list of compilers Musl needs to be compatible > with? Or a set of continuous integration servers? Compatibility with particular compilers should not need to be a consideration except when working on ports to new archs or existing arch-specific code. The language for musl is C99 plus a very minimal subset of "GNU C" features. If you have questions about use of particular language features, don't hesitate to ask if they're okay. Rich