9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] A question on fossil
Date: Thu,  6 Feb 2003 13:11:56 +0000	[thread overview]
Message-ID: <2bc7b99b21f1b2c6f489bbc5a5dd1266@caldo.demon.co.uk> (raw)
In-Reply-To: <A1B93454-39CF-11D7-968A-000393A941BC@ar.aichi-u.ac.jp>

[-- Attachment #1: Type: text/plain, Size: 494 bytes --]

see fossilcons(8).  here's an extract:

          ... The user table records a mapping
          between uids and unames, as well as recording the leader and
          members of each group.  A uid is a string naming a user or
          group and stored in the on-disk data structures.  A uname is
          the string naming a user or group and used in 9P protocol
          messages.  There is a distinction so that unames can be
          safely reused, even though uids cannot.  ...

[-- Attachment #2: Type: message/rfc822, Size: 1818 bytes --]

From: Kenji Arisawa <arisawa@ar.aichi-u.ac.jp>
To: 9fans@cse.psu.edu
Subject: [9fans] A question on fossil
Date: Thu, 6 Feb 2003 21:36:36 +0900
Message-ID: <A1B93454-39CF-11D7-968A-000393A941BC@ar.aichi-u.ac.jp>

Hello,
I have a question on /adm/users of fossil.
It seems that the first field of /adm/users of fossil is same as the
second field.
I don't know whether it must be same or not.
If it must be same, why did you make the format so redundant?
If it must not be same, what is the intent of usage?

Kenji Arisawa

  reply	other threads:[~2003-02-06 13:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06 12:36 Kenji Arisawa
2003-02-06 13:11 ` Charles Forsyth [this message]
2003-02-06 19:27   ` Russ Cox

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=2bc7b99b21f1b2c6f489bbc5a5dd1266@caldo.demon.co.uk \
    --to=forsyth@caldo.demon.co.uk \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).