public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Project:Lisp without members
Date: Wed, 21 Mar 2018 18:55:54 +0100	[thread overview]
Message-ID: <1521654954.1321.9.camel@gentoo.org> (raw)
In-Reply-To: <1521622269.15607.6.camel@gentoo.org>

El mié, 21-03-2018 a las 10:51 +0200, Mart Raudsepp escribió:
> Ühel kenal päeval, L, 10.03.2018 kell 13:26, kirjutas Pacho Ramos:
> > From now Project:Lisp has no members... that doesn't seem an issue as
> > it
> > contains multiple subprojects that maintain relevant packages... but,
> > for the
> > case anyone wants to join the main project...
> > https://wiki.gentoo.org/wiki/Project:Lisp
> 
> This is a valid setup of projects to my knowledge. Please correct me if
> I'm wrong. Don't undertake parent projects if they have subprojects
> with active members please. In other words, please don't undertake a
> project if it has active subprojects, if that was your mails intention
> here.
> https://wiki.gentoo.org/wiki/Project:Lisp even lists subprojects and
> their members as part of lisp project. Though it seems to have gotten a
> direct member now too to prevent the implicit undertaking intention
> (which I think is unnecessary).
> 
> 
There were no "undertaking intention" for that parent project as the mail states
showing no warning about removing it and even suggesting that "it doesn't seem
an issue"... the intention was merely to inform people for the case someone
wanted to joing the Project


      reply	other threads:[~2018-03-21 18:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-10 12:26 [gentoo-dev] Project:Lisp without members Pacho Ramos
2018-03-21  8:51 ` Mart Raudsepp
2018-03-21 17:55   ` Pacho Ramos [this message]

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=1521654954.1321.9.camel@gentoo.org \
    --to=pacho@gentoo.org \
    --cc=gentoo-dev@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