From: Kalin KOZHUHAROV <kalin@thinrope.net>
To: linux-kernel@vger.kernel.org
Cc: linux-ide@vger.kernel.org
Subject: Re: Linux SATA status report updated
Date: Tue, 06 Dec 2005 15:53:55 +0900 [thread overview]
Message-ID: <dn3cj7$c0d$1@sea.gmane.org> (raw)
In-Reply-To: <438E8980.4030800@pobox.com>
Jeff Garzik wrote:
>
> I just updated the Linux SATA status pages with the latest drivers and
> progress:
>
> hardware: http://linux.yyz.us/sata/sata-status.html
> software: http://linux.yyz.us/sata/software-status.html
>
> Let me know if there are any errors or omissions.
Thank you for the time and passion devoted!
I was just thinking and may I suggest if it is not too much hassle, why not add some kind of version
control to those pages?
Lately I am playing with subversion and I am using it at work for such documents (only internal)
with apache. The basic setup allows that your last version is always accessible through HTTP and for
those wanting more (and having proper clearance), svn access allows diffing and log examining.
Yes, I know there is the "Recent Changes" at the top of each document, but sometimes it is too broad.
On the other hand my suggestion might be an overkill. And it might need some time initially (but can
pay later?).
Just my 2 cents, as the saying goes.
Kalin.
--
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|
prev parent reply other threads:[~2005-12-06 6:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 5:26 Linux SATA status report updated Jeff Garzik
2005-12-06 6:53 ` Kalin KOZHUHAROV [this message]
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='dn3cj7$c0d$1@sea.gmane.org' \
--to=kalin@thinrope.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).