From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] Migrating man page to asciidoc?
Date: Mon, 04 Jul 2011 01:28:39 +0200 [thread overview]
Message-ID: <4E10FB27.3080608@gentoo.org> (raw)
In-Reply-To: <4E08A7E0.3090706@gentoo.org>
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. It doesn't have to be a
> quick decision. Also, version control allows us to bring it back if needed.
>
> Ideas on find out who is using 9999:
>
> - Removing 9999 ebuild from the tree and see who's complaining
>
> - Resetting branch master to nothing but a README announcing
> the possible death of that thread and a request to join
> this mailing list and speak up about it if there is need.
>
> - Asking on one/some/all of gentoo-dev, gentoo-user, gentoo forums,
> planet 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. Anyone?
Sebastian
next prev parent reply other threads:[~2011-07-03 23:29 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 0:41 [gentoo-catalyst] Migrating man page to asciidoc? Sebastian Pipping
2011-06-24 7:07 ` Peter Volkov
2011-06-24 17:16 ` Sebastian Pipping
2011-06-25 17:30 ` Matt Turner
2011-06-25 17:50 ` Sebastian Pipping
2011-06-25 18:31 ` Matt Turner
2011-06-26 2:02 ` Matt Turner
2011-06-26 2:36 ` Sebastian Pipping
2011-06-26 2:49 ` William Hubbs
2011-06-26 3:14 ` Sebastian Pipping
2011-06-26 3:36 ` William Hubbs
2011-06-26 3:46 ` William Hubbs
2011-06-26 3:59 ` Sebastian Pipping
2011-06-26 3:49 ` Sebastian Pipping
2011-06-26 4:33 ` William Hubbs
2011-06-26 4:57 ` Sebastian Pipping
2011-06-26 15:44 ` Matt Turner
2011-06-26 17:33 ` William Hubbs
2011-06-26 17:55 ` Peter Stuge
2011-06-26 18:02 ` Matt Turner
2011-06-26 18:08 ` Peter Stuge
2011-06-26 23:01 ` Matt Turner
2011-06-26 23:26 ` Jorge Manuel B. S. Vicetto
2011-06-27 0:00 ` Peter Stuge
2011-06-27 0:31 ` Jorge Manuel B. S. Vicetto
2011-06-27 1:06 ` Peter Stuge
2011-06-27 1:43 ` Sebastian Pipping
2011-06-27 3:58 ` Jorge Manuel B. S. Vicetto
2011-06-27 15:55 ` Sebastian Pipping
2011-07-03 23:28 ` Sebastian Pipping [this message]
2011-07-04 0:10 ` Matt Turner
2011-07-04 0:18 ` Sebastian Pipping
2011-06-27 0:39 ` Peter Stuge
2011-06-26 17:55 ` Matt Turner
2011-06-26 18:17 ` Sebastian Pipping
2011-06-26 19:25 ` William Hubbs
2011-06-26 4:10 ` Matt Turner
2011-06-26 4:14 ` Sebastian Pipping
2011-06-26 4:44 ` William Hubbs
2011-06-26 4:46 ` Sebastian Pipping
2011-06-27 6:33 ` Peter Volkov
2011-06-26 16:48 ` Sebastian Pipping
2011-06-26 17:04 ` Peter Stuge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E10FB27.3080608@gentoo.org \
--to=sping@gentoo.org \
--cc=gentoo-catalyst@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox