From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 36AED138334 for ; Thu, 10 Oct 2019 12:16:32 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AA6D3E089A; Thu, 10 Oct 2019 12:16:27 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 6903BE0884 for ; Thu, 10 Oct 2019 12:16:27 +0000 (UTC) Received: from pomiot (c134-66.icpnet.pl [85.221.134.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 3616034BAEB; Thu, 10 Oct 2019 12:16:25 +0000 (UTC) Message-ID: <7c7759a24cf550462a2be8ed65053fdf6627c4d2.camel@gentoo.org> Subject: Re: [gentoo-dev] What is the source for https://dev.gentoo.org/~hollow/distfiles/genqmail-* From: =?UTF-8?Q?Micha=C5=82_G=C3=B3rny?= To: gentoo-dev@lists.gentoo.org, net-mail@gentoo.org Date: Thu, 10 Oct 2019 14:16:21 +0200 In-Reply-To: <7519216.COF0g6uIjq@daneel.sf-tec.de> References: <1818672.QCxIfCrqvl@daneel.sf-tec.de> <1621500.IZWtrvyDm3@daneel.sf-tec.de> <348E33BB-7944-47F7-8DB7-2FEBB011F36E@gentoo.org> <7519216.COF0g6uIjq@daneel.sf-tec.de> Organization: Gentoo Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-efg0izuKVmcaac18gZI5" User-Agent: Evolution 3.32.4 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 X-Archives-Salt: a4232ae2-f848-4f4b-ac51-1ce2234208e7 X-Archives-Hash: a4b2e2c95fa19e8ec4d0610833340b13 --=-efg0izuKVmcaac18gZI5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, 2019-10-10 at 12:31 +0200, Rolf Eike Beer wrote: > Am Donnerstag, 10. Oktober 2019, 12:15:09 CEST schrieb Micha=C5=82 G=C3= =B3rny: > > Dnia October 10, 2019 9:39:38 AM UTC, Rolf Eike Beer = =20 > napisa=C5=82(a): > > > Am Samstag, 21. September 2019, 10:50:07 CEST schrieb Rolf Eike Beer: > > > > Hi, > > > >=20 > > > > I'm planning to do some cleanups to the qmail stuff. One thing s th= at the > > > > genqmail tarball is from 20080406 and needs to be patched itself, w= hich > > > > makes things complicated. So, does anyone know what was the source = of > > > > these tarballs? I can't look into the directory, maybe there are ev= en > > > > older ones? > > > > Otherwise I would propose to just start a new git repo for that and= do a > > > > new snapshot with the patches already incorporated. > > >=20 > > > So I guess noone knows. Can someone assist me in creating a new upstr= eam? I > > > have created a new git repository with the original tarball and the 2= =20 > > > existing patches, which can be found here:=20 > > > https://github.com/DerDakon/genqmail > > >=20 > > > Please pick this up and move it somewhere into Gentoo git infrastruct= ure. I > > > can transfer ownership to the Github Gentoo organization if you would= like. > > > Afterwards I just need someone to push the button and create a new sn= apshot > > > from that (preferably together with a git tag). > >=20 > > Is there really a reason to do that? Since you're maintaining it, just = keep > > it on your gh. >=20 > I just want to prevent that the same thing happens again. >=20 I don't see a difference between a stale repo on your GitHub account and a stale repo on Gentoo Infra. Except the former is easy to fork, and the latter we have in dozens, and nobody knows what to do with them. --=20 Best regards, Micha=C5=82 G=C3=B3rny --=-efg0izuKVmcaac18gZI5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQGTBAABCgB9FiEEx2qEUJQJjSjMiybFY5ra4jKeJA4FAl2fIRVfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM3 NkE4NDUwOTQwOThEMjhDQzhCMjZDNTYzOUFEQUUyMzI5RTI0MEUACgkQY5ra4jKe JA6IKAf+PdVyS4baCkQjAEslYICZ5l2sLV0k58z2HZHvxX9NVx+yeuv6t8DgCCM8 tOZG0Sw2yBCFLoj72qgeWvV9W8jMen8ylAjK1l1w0ftsoE0013CKglm+8hAMsfrc sSz2GIsolRysLXmvtGgoj+xoSWNvnMaDsDud7NENAgFzutJcPr83SBR7Y5nkUAg8 ZIY3GI7NZdNfbzB8LQfS2/V47lMWsnsY22RA4UL1/IXRdvP0Jj6IGIk5VJtpyHm2 GRDhLn45zfliGw4etcJvadpfhk+GxC/gbaG21YjrDNQ6nyuRqAIB6gjNh+cD6A0i mK5GCEwICiKvqfnV+m2JrDXl7zmiPQ== =Pn0N -----END PGP SIGNATURE----- --=-efg0izuKVmcaac18gZI5--