From: Stan Shebs <shebs@apple.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jim Blandy <jimb@red-bean.com>, gdb@sources.redhat.com
Subject: Re: History before 1999
Date: Mon, 09 Jan 2006 17:10:00 -0000 [thread overview]
Message-ID: <43C298BF.6070209@apple.com> (raw)
In-Reply-To: <uoe2ng8v0.fsf@gnu.org>
Eli Zaretskii wrote:
>>Date: Sat, 7 Jan 2006 09:13:59 -0800
>>From: Jim Blandy <jimb@red-bean.com>
>>Cc: gdb@sources.redhat.com
>>
>>So, I don't think there's any way for you to get history farther back.
>>
>
>Too bad. Fortunately, there are old GDB releases in the old-releases
>directory of the sourceware server, so I guess I could use them as
>snapshots of the old repository.
>
>Thanks for the feedback.
>
In theory, an energetic person could graft old public releases into
the repository, making a sort of synthetic history. Easier in SVN
perhaps?
Didn't we do regular snapshots in between releases? If anybody
still has those around, they could supplement the release history.
Stan
next prev parent reply other threads:[~2006-01-09 17:10 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
2006-01-07 19:10 ` Eli Zaretskii
2006-01-09 17:10 ` Stan Shebs [this message]
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=43C298BF.6070209@apple.com \
--to=shebs@apple.com \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jimb@red-bean.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