public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: foser <foser@foser.dyn.warande.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] desktop
Date: Fri, 29 Aug 2003 00:32:03 +0200	[thread overview]
Message-ID: <1062109922.14186.2.camel@rivendell> (raw)
In-Reply-To: <20030828233453.07652b52.spider@gentoo.org>

On Thu, 2003-08-28 at 23:34, Spider wrote:
> begin  quote
> On Thu, 28 Aug 2003 22:46:34 +0200
> dams@idm.fr wrote:
> 
> 
> > it shows... It shows that I applied some of my leader rule : come with
> > a already built idea, let people be desapointed, let them argue,
> > fight, so that they defend their point of views, and collect the
> > conclusions.
> 
> 
> I should point out that this is also discouraged against because it
> fosters an "aggressive culture" and dissent within development teams,
> and may also undermine faith, whereas the method of carefully selecting
> points one at a time for discussion will work far smoother and with less
> irregularities, however may not be as immediate?

And i very much doubt that was your initial intent. If you really had
done that on purpose, you would never have mentioned it. Nice try.

- foser


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-08-28 22:37 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-27 22:22 [gentoo-dev] desktop dams
2003-08-27 22:58 ` Spider
2003-08-28  0:41   ` Brett I. Holcomb
2003-08-28  0:47     ` Jon Portnoy
2003-08-28  0:58       ` Cedric Veilleux
2003-08-28  1:29       ` Riyad Kalla
2003-08-28  1:48       ` Stuart Herbert
2003-08-28  8:08   ` dams
2003-08-28 10:25     ` Paul de Vrieze
2003-08-28 10:51       ` dams
2003-08-28 11:08         ` Paul de Vrieze
2003-08-28 11:28           ` dams
2003-08-28 13:37             ` Mike Frysinger
2003-08-29  5:22               ` Luke-Jr
2003-08-28 11:15 ` foser
2003-08-28 12:52   ` dams
2003-08-28 13:21     ` foser
2003-08-28 13:51       ` Stuart Herbert
2003-08-28 14:00       ` Paul de Vrieze
2003-08-28 14:10         ` Michael Cummings
2003-08-28 14:34           ` foser
2003-08-28 14:30         ` foser
2003-08-28 17:44         ` Spider
2003-08-28 19:14           ` Peter Ruskin
2003-08-28 19:24             ` foser
2003-08-28 22:07               ` Peter Ruskin
2003-08-28 20:46             ` dams
2003-08-28 21:34               ` Spider
2003-08-28 22:32                 ` foser [this message]
2003-08-28 23:01                   ` dams
2003-08-28 20:35           ` dams
2003-08-28 21:03             ` Spider
2003-08-28 21:21               ` dams
2003-08-28 22:40                 ` foser
2003-08-28 21:07           ` Paul de Vrieze
2003-08-28 14:59       ` dams
2003-08-28 21:17         ` Paul de Vrieze
2003-08-28 23:24       ` Jason Stubbs
2003-08-28 13:54     ` Chris Gianelloni
2003-08-28 15:03       ` dams
2003-08-28 15:09         ` Stuart Herbert
2003-08-28 15:36           ` dams
2003-08-28 15:48             ` jonah benton
2003-08-28 14:04   ` Paul de Vrieze
2003-08-28 14:48     ` foser
2003-08-28 23:30       ` Seemant Kulleen
2003-08-29  1:32         ` Luke-Jr
2003-08-29 14:06           ` dams
2003-08-29 14:18             ` Luke-Jr

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=1062109922.14186.2.camel@rivendell \
    --to=foser@foser.dyn.warande.net \
    --cc=gentoo-dev@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