Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
Subject: Re: Was I dreaming...?
Date: Mon, 28 Jan 2002 20:40:25 +0100	[thread overview]
Message-ID: <873d0qz2l2.fsf@bang.priv.no> (raw)
In-Reply-To: <m1ofjewbwa.fsf@reader.newsguy.com>

>>>>> Harry Putnam <reader@newsguy.com>:

> I know very little cvs but looking thru the docs, looks like I ask
> for a certain revision, but it wasn't that clear how (the syntax)
> and how first to determine what version is current.

Files may have a sticky tag, locking it to a particular version, or
branch.  If you do
	cd wherever/gnus/
	cvs up -A
	cvs up -dP
you should be at the head of the trunk (aka. "main branch") of Gnus.

...if that's what you wanted to do...? :-)

> For the last part, is `cvs status' the only way?  Can it be aimed at
> less than `cvs status' ... That is lots of output.  Is there
> something that just tells the whole gnus module's current version
> number?

Not really, but you can do this:

Open a Gnus .el file in GNU emacs (I don't think XEmacs has this, but
for both GNU emacs, and XEmacs, "PCL-CVS" is recommended if you plan
to use CVS).

Observe that on the status bar it says "(Emacs-Lisp CVS-someversionnumber)"

Do `C-x v l'.  This will display the CVS log of the file.

Go to the start of the buffer displaying the log.  See the text
"symbolic names:".  Under that text, all tags in the CVS file for this
file, are listed.  When larsi stamp a particular release of Gnus, he
puts a tag for that release on a particular version of all files that
belong to the release.

> cvs status gnus  tells me it knows nothing about gnus

cd to the top level directory of your gnus checkout, and type "cvs
status".  That's probably what you're looking for.





  reply	other threads:[~2002-01-28 19:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-28 18:22 Harry Putnam
2002-01-28 18:29 ` Karl Kleinpaste
2002-01-28 18:47   ` Harry Putnam
2002-01-28 19:40     ` Steinar Bang [this message]
2002-01-29  1:47       ` Harry Putnam
2002-01-29  2:38         ` Russ Allbery
2002-01-29  9:50           ` Kai Großjohann
2002-01-29  9:51         ` Kai Großjohann
2002-01-28 18:57   ` Josh Huber
2002-01-28 19:13     ` Karl Kleinpaste
2002-01-30  8:34       ` Matthieu Moy
2002-01-30  9:05         ` Harry Putnam
2002-01-28 19:22     ` Harry Putnam
2002-01-28 21:16       ` ShengHuo ZHU
2002-01-28 21:43         ` Josh Huber
2002-01-28 22:30           ` ShengHuo ZHU
2002-01-29  0:31             ` Josh Huber
2002-01-29  1:18               ` ShengHuo ZHU
2002-01-28 18:33 ` Harry Putnam
2002-01-28 20:00 ` Robert Marshall
2002-01-28 20:58 ` Reiner Steib
2002-01-29  2:01   ` Harry Putnam
2002-01-29 14:19     ` Yair Friedman (Jerusalem)
2002-01-29 14:51       ` Reiner Steib

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=873d0qz2l2.fsf@bang.priv.no \
    --to=sb@dod.no \
    /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).