X-Original-To: alpine-aports@lists.alpinelinux.org Received: from mx1.tetrasec.net (mx1.tetrasec.net [74.117.190.25]) by lists.alpinelinux.org (Postfix) with ESMTP id EA7F2F815B9 for ; Wed, 20 Feb 2019 12:11:44 +0000 (UTC) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id 614299E1EBE; Wed, 20 Feb 2019 12:11:44 +0000 (UTC) Received: from ncopa-desktop.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: alpine@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id 1F8C79E0400; Wed, 20 Feb 2019 12:11:42 +0000 (UTC) Date: Wed, 20 Feb 2019 13:11:38 +0100 From: Natanael Copa To: Andrew Bell Cc: ghostbar@riseup.net, alpine-aports@lists.alpinelinux.org Subject: Re: [alpine-aports] PR Merge? Message-ID: <20190220131138.618fd73c@ncopa-desktop.copa.dup.pw> In-Reply-To: References: X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-alpine-linux-musl) X-Mailinglist: alpine-aports Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi, You can send patch via github PR or via git send-email to alpine-aports mailing list. If you have a trivial patch you can also do: `git format-patch -1 --stdout | tpaste` and post the URL on IRC Freenode #alpine-devel channel if you have the attention of a developer with git push access. I have been on vacation for a month and we have been pretty busy with the 3.9 release so we have falling behind with the PR queue. Sorry for that. Do you have the URL to the github PR? -nc On Sat, 16 Feb 2019 20:02:33 -0500 Andrew Bell wrote: > It would be nice if this was clear on this page: > https://wiki.alpinelinux.org/wiki/Creating_an_Alpine_package > > The implication is that you can make a PR from the github repo. > > Thanks, > > On Sat, Feb 16, 2019 at 5:31 PM wrote: > > > Hi Andrew, > > > > You need to send a patch to the aports mailing lists. The PR method is > > not used for contributions in alpine. You can read more on how to it > > here: https://wiki.alpinelinux.org/wiki/Creating_patches > > > > On 2019-02-14 09:59, Andrew Bell wrote: > > > Hi, > > > > > > I made a PR from to the github aports repo a while ago and haven't > > > heard anything. There seem to be a lot of PRs there just waiting with > > > no feedback. Is there a part of the process that I'm not > > > understanding to get a PR merged? Do you need help to manage these > > > changes? > > > > > > Thanks, > > > > > > -- > > > Andrew Bell > > > andrew.bell.ia@gmail.com > > > > > > --- > > Unsubscribe: alpine-aports+unsubscribe@lists.alpinelinux.org > > Help: alpine-aports+help@lists.alpinelinux.org > > --- > > > > > --- Unsubscribe: alpine-aports+unsubscribe@lists.alpinelinux.org Help: alpine-aports+help@lists.alpinelinux.org ---