From: Roman Shaposhnik <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Quick question on sources.cs.bell-labs.com
Date: Sat, 27 Dec 2008 14:19:31 -0800 [thread overview]
Message-ID: <1CE7AA9A-3864-4EE1-8FC0-5EDC15A85788@sun.com> (raw)
I thought that sources is a general purpose fossil server that archives
everything in venti dumps, but apparently not:
term% 9fs sourcesdump
term% ls -l /n/sourcesdump/2008/1225/dist/replica
term%
In fact, if one looks at the /n/sources/dist/replica it seems
that the directory itself was last modified on Nov 23, but
the files are from Nov 18:
term% ls -ld /n/sources/dist/replica
d-rwxrwxr-x M 22 glenda sys 0 Nov 23 23:00 /n/sources/dist/replica
term%
--rw-rw-r-- M 22 glenda sys 922 Nov 18 23:01 /n/sources/dist/
replica/cd
d-rwxrwxr-x M 22 glenda sys 0 Nov 18 23:01 /n/sources/dist/
replica/client
--rw-rw-r-- M 22 glenda sys 237 Nov 18 23:01 /n/sources/dist/
replica/fossil
--rwxrwxr-x M 22 glenda sys 542 Nov 18 23:01 /n/sources/dist/
replica/inst
--rwxrwxr-x M 22 glenda sys 1086 Nov 18 23:01 /n/sources/dist/
replica/network
--rw-rw-r-- M 22 geoff sys 5763789 Nov 18 23:31 /n/sources/dist/
replica/sources.db
--rw-rw-r-- M 22 geoff sys 7158415 Nov 18 23:28 /n/sources/dist/
replica/sources.log
So, I tried:
term% ls -l /n/sourcesdump/2008/1123/dist/replica
term% ls -l /n/sourcesdump/2008/1124/dist/replica
term% ls -l /n/sourcesdump/2008/1118/dist/replica
ls: /n/sourcesdump/2008/1118/dist/replica: '/n/sourcesdump/
2008/1118/dist' does not exist
term% ls -l /n/sourcesdump/2008/1119/dist/replica
term%
Only to be surprised some more.
Any explanation?
Thanks,
Roman.
next reply other threads:[~2008-12-27 22:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-27 22:19 Roman Shaposhnik [this message]
2008-12-27 22:38 ` erik quanstrom
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=1CE7AA9A-3864-4EE1-8FC0-5EDC15A85788@sun.com \
--to=rvs@sun.com \
--cc=9fans@9fans.net \
/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).