From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1QdWkd-0006PY-Qh for garchives@archives.gentoo.org; Mon, 04 Jul 2011 00:11:00 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E7E2321C05D; Mon, 4 Jul 2011 00:10:40 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id A3A6821C05D for ; Mon, 4 Jul 2011 00:10:40 +0000 (UTC) Received: from mail-vx0-f181.google.com (mail-vx0-f181.google.com [209.85.220.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mattst88) by smtp.gentoo.org (Postfix) with ESMTPSA id 08CD31B4007 for ; Mon, 4 Jul 2011 00:10:39 +0000 (UTC) Received: by vxa40 with SMTP id 40so4325086vxa.40 for ; Sun, 03 Jul 2011 17:10:33 -0700 (PDT) Received: by 10.52.24.66 with SMTP id s2mr748038vdf.196.1309738233095; Sun, 03 Jul 2011 17:10:33 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-catalyst@lists.gentoo.org Reply-to: gentoo-catalyst@lists.gentoo.org MIME-Version: 1.0 Received: by 10.52.158.168 with HTTP; Sun, 3 Jul 2011 17:10:13 -0700 (PDT) In-Reply-To: <4E10FB27.3080608@gentoo.org> References: <20110626024929.GA6506@linux1> <4E06A41E.6000705@gentoo.org> <20110626033613.GA6577@linux1> <4E06AC3D.4000901@gentoo.org> <20110626043329.GA6710@linux1> <4E06BC27.3020808@gentoo.org> <20110626173348.GA8371@linux1> <20110626175504.4199.qmail@stuge.se> <4E07C031.1030004@gentoo.org> <20110627000035.10174.qmail@stuge.se> <4E07CF74.5020900@gentoo.org> <4E07E039.1000308@gentoo.org> <4E07FFCC.4090109@gentoo.org> <4E08A7E0.3090706@gentoo.org> <4E10FB27.3080608@gentoo.org> From: Matt Turner Date: Mon, 4 Jul 2011 00:10:13 +0000 Message-ID: Subject: Re: [gentoo-catalyst] Migrating man page to asciidoc? To: gentoo-catalyst@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: X-Archives-Hash: 8dddb450ec916f25883ab95f230d28b7 On Sun, Jul 3, 2011 at 11:28 PM, Sebastian Pipping wrote= : > On 06/27/2011 05:55 PM, Sebastian Pipping wrote: >> On 06/27/2011 05:58 AM, Jorge Manuel B. S. Vicetto wrote: >>> We use 2.0.6.916 on official releng releases. >>> I tried 9999 on my private tests because [..] >> >> To me that leaves the question who uses 9999 for serious stuff at all. >> In case it's no one (which we should find out) we could trash that >> branch and fully concentrate on calalyst_2. >> >> I guess that sounds a bit radical at first. =A0It doesn't have to be a >> quick decision. =A0Also, version control allows us to bring it back if n= eeded. >> >> Ideas on find out who is using 9999: >> >> =A0- Removing 9999 ebuild from the tree and see who's complaining >> >> =A0- Resetting branch master to nothing but a README announcing >> =A0 =A0the possible death of that thread and a request to join >> =A0 =A0this mailing list and speak up about it if there is need. >> >> =A0- Asking on one/some/all of gentoo-dev, gentoo-user, gentoo forums, >> =A0 =A0planet gentoo. >> >> After such action I imagine a time window of 2 to 4 weeks to give people >> a chance to react. >> >> What do you think? >> >> >>> I can confirm that the build with the master branch fails as it doesn't >>> seem able to find the spec files or doesn't accept them - the official >>> ones we use to build weekly releases. >> >> That seems to further decrease the chance that someone is using 9999 for >> real to me. > > One week has passed by. =A0Anyone? I'm perfectly fine with the change, especially after the graphviz dependency of asciidoc was made optional. Matt