public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Joseph Myers <jsm28@cam.ac.uk> To: gcc-gnats@gcc.gnu.org Cc: jsm28@cam.ac.uk Subject: other/3348: Corrupt /cvs/gcc/gcc/gcc/ChangeLog,v Date: Thu, 21 Jun 2001 15:16:00 -0000 [thread overview] Message-ID: <E15DCaz-0006Uw-00@jsm28.trin.cam.ac.uk> (raw) >Number: 3348 >Category: other >Synopsis: Corrupt /cvs/gcc/gcc/gcc/ChangeLog,v >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Jun 21 15:16:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Joseph S. Myers >Release: 3.0 >Organization: none >Environment: System: Linux digraph 2.2.19 #1 Wed Mar 28 16:01:38 UTC 2001 i686 unknown Architecture: i686 host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: i686-pc-linux-gnu configured with: ../gcc-3.0/configure --prefix=/usr --with-slibdir=/lib --enable-shared --enable-threads=posix --with-system-zlib >Description: /cvs/gcc/gcc/gcc/ChangeLog,v is corrupt, preventing checkouts of EGCS 1.0.1 using the tag we document in the GCC web pages. This has been noted on the gcc list by a user trying to check out on that tag, and previously reported to overseers (to which I'll assign this PR). >How-To-Repeat: Try to check out an affected revision, or run cvs log on rlog on the file. >Fix: Restore the relevant revisions from a backup tape of suitable vintage. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-06-21 15:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-21 15:16 Joseph Myers [this message] 2001-06-21 16:24 jsm28 2001-07-12 14:03 geoffk
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=E15DCaz-0006Uw-00@jsm28.trin.cam.ac.uk \ --to=jsm28@cam.ac.uk \ --cc=gcc-gnats@gcc.gnu.org \ /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: linkBe 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).