public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Damon M. Conway" <damon@chiba.3jane.net>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Problem adding user + Internationalization
Date: Tue Oct 30 09:29:01 2001	[thread overview]
Message-ID: <200110301628.f9UGSLs10699@chiba.3jane.net> (raw)
In-Reply-To: <1004402721.2792.14.camel@katios.nolabel.net>

>Let me explain myself. I was used to type 'useradd nick' to add a user
>with dir & co. So i tought (wrong it seems, and the error message didn't
>help me), that there was a bug. And i never thought a user list was the
>right place for bug report (btw, if gentoo-user is a good place for bug
>report, please tell me, thanks in advance), so i posted my problem here.
>Concerning the other question, you are right, this is not the good
>place, i thought of this thing just before sending the message, and
>didn't even think that there was a list more suited for this (but i was
>already a subscriber of gentoo-user.. not a excellent memory ;) (the
>next time i'll browse better in the portage tree, the answer was there..
>humm).

No need to explain.  Until recently, this list was the only discussion list
for gentoo.  I would post to gentoo-user about issues first to actually
determine if it is a bug.  Perhaps it's a case like this where you were
missing a flag or something.  Once it's determined to be a bug, a detailed
bug report should be posted to gentoo-dev.  Hopefully, we'll have a
bug-tracking system setup for taking in bug reports in a consistent
fashion.

>Btw, it's odd to see that all my questions that i thought were really
>dev-related (install/system questions, plans, hotplug) were not
>answered, unlike the not-so-dev-related ones. Don't misunderstand me, i
>really appreciate your answers (thanks all!), i just find this strange.

I saw your questions, but wanted to let drobbins comment on them.  He
creates/coordinates the install images.  I imagine others felt the same
way.

>Thanks again everyone, and sorry for my 'bad' questions, I'll try to
>answer my future ones by myself (or elsewhere).

Don't get me wrong.  You're questions are fine.  I'm just trying to remind
everyone of the gentoo-user list so we can separate the functionality.

kabau

--
"UNIX was not designed to stop you from doing stupid things, because that
 would also stop you from doing clever things."  --Doug Gwyn



  reply	other threads:[~2001-10-30 16:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-26 15:51 [gentoo-dev] Newbie + e3? + keymap? Sylvain OBEGI
2001-10-26 16:38 ` [gentoo-dev] s.q.u.e.l.c.h ebuild James M Long
2001-10-27 12:10   ` Martin Schlemmer
2001-10-26 16:45 ` [gentoo-dev] Newbie + e3? + keymap? Daniel Robbins
2001-10-27  9:35   ` Sylvain OBEGI
2001-10-28 15:03     ` [gentoo-dev] Problem adding user + Internationalization Sylvain OBEGI
2001-10-29  6:50       ` Dan Armak
2001-10-29  9:59       ` Damon M. Conway
2001-10-29 17:46         ` Sylvain OBEGI
2001-10-30  9:29           ` Damon M. Conway [this message]
2001-10-30  9:49             ` Djamil ESSAISSI
2001-10-30  9:52               ` Damon M. Conway
2001-10-30  9:57                 ` Djamil ESSAISSI
2001-10-30 10:13                   ` Daniel Robbins

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=200110301628.f9UGSLs10699@chiba.3jane.net \
    --to=damon@chiba.3jane.net \
    --cc=gentoo-dev@cvs.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