public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: website & identifiers
Date: Sat, 27 Dec 2003 18:43:00 -0000	[thread overview]
Message-ID: <3FEDBDBF.3090204@msu.edu> (raw)
In-Reply-To: <Pine.BSI.4.53.0312270656501.5402@mail.his.com>

Thomas Dickey wrote:

> When perusing the website for news, it would be useful if the pages were
> marked (in their source) as generated or manually updated.  For the former
> (unless they're generated on demand), a modification date would also be
> useful.  For the latter, an RCS/CVS/etc identifier to distinguish
> successive versions is normally expected.
> 
> Are the pages all generated from another format, or are some in CVS
> (somewhere)?

By the way... what are you looking for?  CVS identifiers wouldn't 
necessarily help to determine that new information has been posted since 
commits for spelling fixes, grammar changes, dead link correction, etc. 
would cause irrelevant noise in the modified date tags.  That's really 
why I chose to put a hand-coded date at the top of the pages; that way 
people are notified when content has been modified in a meaningful way, 
but there aren't false-positives when minor changes have been made.

Would CVS identifiers still be useful for whatever you are trying to do? 
    Maybe I'll start adding them as comments for starters but still keep 
the hand-modified date for each page.

Harold


  parent reply	other threads:[~2003-12-27 17:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-27 15:34 Thomas Dickey
2003-12-27 17:27 ` Harold L Hunt II
2003-12-27 18:43 ` Harold L Hunt II [this message]
2003-12-29 19:30   ` Thomas Dickey
2003-12-29 19:34   ` Thomas Dickey
2003-12-29 19:38     ` Harold L Hunt II
2003-12-29 20:51       ` Thomas Dickey

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=3FEDBDBF.3090204@msu.edu \
    --to=huntharo@msu.edu \
    --cc=cygwin-xfree@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).