On Fri, May 17, 2013 at 10:39 AM, Óscar Fuentes <ofv at wanadoo.es> wrote:> > Apart from that, the most correct place for submitting patches is either > the llvm-commits mailing list or the bug database. > >We don't accept patches through the bug database. Patches should be sent to llvm-commits for review. -- Sean Silva -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130517/f3ddb3fd/attachment.html>
Sean Silva <silvas at purdue.edu> writes:> We don't accept patches through the bug database. Patches should be sent to > llvm-commits for review.Not even patches for fixing bugs? For instance: creating a bug report with "the build is broken in X, the attached patch fixes it."
On Fri, May 17, 2013 at 12:21 PM, Óscar Fuentes <ofv at wanadoo.es> wrote:> Sean Silva <silvas at purdue.edu> writes: > >> We don't accept patches through the bug database. Patches should be sent to >> llvm-commits for review. > > Not even patches for fixing bugs? For instance: creating a bug report > with "the build is broken in X, the attached patch fixes it." >No really, that relies on someone looking at the bug report who is also a person that can and wants to review it and that it's perfect on the first go. Pretty small odds. -eric
On 17 May 2013 20:21, Óscar Fuentes <ofv at wanadoo.es> wrote:> Not even patches for fixing bugs? For instance: creating a bug report > with "the build is broken in X, the attached patch fixes it." >Attaching patches to bugs is fine when you want to share a potential or incomplete patch. If you want your patch to be considered for review and be committed, you must email to either llvm-commits or cfe-commits (or both). cheers, --renato -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130517/8fb53af6/attachment.html>