From: Neil Crellin <neilc@wallaby.cc>
Subject: Re: Identifying CVS version (was: Re: crash)
Date: 01 Mar 2000 15:00:17 -0800 [thread overview]
Message-ID: <vb6zosiguta.fsf@webtile.wallaby.cc> (raw)
In-Reply-To: lconrad@world.std.com's message of "01 Mar 2000 09:54:29 -0500"
lconrad <lconrad@world.std.com> writes:
>>>>>> "Jan" == Jan Vroonhof <vroonhof@math.ethz.ch> writes:
> Jan> If it is a crash, then it is xemacs and you need to give more
> Jan> info. C backtrace and version to be precise ('latest cvs' is
> Jan> very ambiguous)
> Is there a way we can be more precise easily? That is, "latest cvs as
> of date/time" is clearly more precise, but is there something that
> would be more useful to someone who wanted to check out the precise
> version?
> And if we know it's the "latest CVS as of last week some time", is
> there a file we can use to identify the precise time last week?
Assuming we can trust those with checkin privs to make ChangeLog entries
as they update, perhaps `head -3 gnus/lisp/ChangeLog` might suffice?
-Neil
next prev parent reply other threads:[~2000-03-01 23:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-01 3:59 crash Michael Harnois
2000-03-01 8:13 ` crash Jan Vroonhof
2000-03-01 14:54 ` Identifying CVS version (was: Re: crash) lconrad
2000-03-01 23:00 ` Neil Crellin [this message]
2000-03-03 17:33 ` Jan Vroonhof
2000-03-02 15:38 ` crash Michael Harnois
2000-03-02 17:01 ` crash Jan Vroonhof
2000-03-02 20:06 ` crash Michael Harnois
2000-03-03 8:39 ` crash Jan Vroonhof
2000-03-03 15:13 ` crash Michael Harnois
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=vb6zosiguta.fsf@webtile.wallaby.cc \
--to=neilc@wallaby.cc \
/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).