From: Jim Blandy <jimb@red-bean.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: History before 1999
Date: Sat, 07 Jan 2006 17:14:00 -0000 [thread overview]
Message-ID: <8f2776cb0601070913q365de93g8d80a4886050cba1@mail.gmail.com> (raw)
In-Reply-To: <uy81sfhwq.fsf@gnu.org>
On 1/7/06, Eli Zaretskii <eliz@gnu.org> wrote:
> "cvs log" shows that the oldest version of GDB sources for which
> there's information in the CVS is from April 1999. Is there any
> reasonably uncomplicated way to do the equivalent of "cvs diff" and
> "cvs annotate" for older versions?
Was it really 1999? Anyway, before sourceware.org got started, the
only revision controlled history was in Cygnus's private CVS
repository. That was mixed in with various NDA'd stuff, including
some in the core files of GDB, so we couldn't publish the whole
history without a lot of work sanitizing it.
So, I don't think there's any way for you to get history farther back.
next prev parent reply other threads:[~2006-01-07 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 10:31 Eli Zaretskii
2006-01-07 17:14 ` Jim Blandy [this message]
2006-01-07 19:10 ` Eli Zaretskii
2006-01-09 17:10 ` Stan Shebs
2006-01-09 20:33 ` Jim Blandy
2006-01-09 22:56 ` Daniel Jacobowitz
2006-01-10 0:12 ` Ian Lance Taylor
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=8f2776cb0601070913q365de93g8d80a4886050cba1@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.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