From: YAMANASHI Takeshi <9.nashi@gmail.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Patch notification emails
Date: Mon, 5 Sep 2005 10:49:35 +0900 [thread overview]
Message-ID: <915dfc91aadb65861b6deb01c6f6c5c0@orthanc.cc.titech.ac.jp> (raw)
> > http://angband.tip9ug.jp/magic/histgw/n/sources/plan9/sys/src/cmd/tcs/utf.c
> > (see the [none] and [rsc] at the end of different changes)
> This is because they are copying sources themselves,
Yes. Actually, a user which is not listed in the /adm/users on
the sources is doing replica/pull. Therefore, muids of updated
files are always [none].
Is there a way to preserve muid on doing replica/pull? Thanks.
--
next reply other threads:[~2005-09-05 1:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 1:49 YAMANASHI Takeshi [this message]
2005-09-05 2:32 ` Russ Cox
-- strict thread matches above, loose matches on Subject: below --
2005-09-04 12:14 Uriel
[not found] ` <ee9e417a05090405316c2f7bab@mail.gmail.com>
2005-09-04 12:39 ` Uriel
2005-09-04 12:59 ` Russ Cox
2005-09-04 13:09 ` Uriel
2005-09-05 1:15 ` 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=915dfc91aadb65861b6deb01c6f6c5c0@orthanc.cc.titech.ac.jp \
--to=9.nashi@gmail.com \
--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).