public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk> To: bosch@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: ada/6558: [mainline regression] Wrongly reverted patches Date: Tue, 29 Oct 2002 02:36:00 -0000 [thread overview] Message-ID: <20021029103605.6208.qmail@sources.redhat.com> (raw) The following reply was made to PR ada/6558; it has been noted by GNATS. From: "Joseph S. Myers" <jsm28@cam.ac.uk> To: Zack Weinberg <zack@codesourcery.com> Cc: Nathanael Nerode <neroden@twcny.rr.com>, <gcc-gnats@gcc.gnu.org>, <bosch@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org> Subject: Re: ada/6558: [mainline regression] Wrongly reverted patches Date: Tue, 29 Oct 2002 10:27:44 +0000 (GMT) On Mon, 28 Oct 2002, Zack Weinberg wrote: > My understanding is that the only patches at issue were those lost > when this change occurred: > > 2002-03-07 Geert Bosch <bosch@gnat.com> Yes. It's all patches from non-ACT people to the FSF tree before then that need to be checked to make sure they are still in the tree or have been superseded by subsequent changes. I think someone found an example (which may or may not now have been unreverted individually) that wasn't among the examples I gave of patches wrongly reverted by this change, so it is necessary to do that check rather than relying on my list. > I would like to point out that it is just shy of eight months since > this happened, and there has been no indication that Mr. Bosch has > lifted a finger to address the problem that he created (beyond > claiming that it would be fixed soon). -- Joseph S. Myers jsm28@cam.ac.uk
next reply other threads:[~2002-10-29 10:36 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-29 2:36 Joseph S. Myers [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-20 3:06 neroden 2002-10-29 13:16 Geert Bosch 2002-10-29 13:06 Nathanael Nerode 2002-10-29 13:06 Geert Bosch 2002-10-29 12:56 Nathanael Nerode 2002-10-29 12:46 Nathanael Nerode 2002-10-28 23:26 Zack Weinberg 2002-10-28 23:06 Nathanael Nerode
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=20021029103605.6208.qmail@sources.redhat.com \ --to=jsm28@cam.ac.uk \ --cc=bosch@gcc.gnu.org \ --cc=gcc-prs@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).