public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com> To: bosch@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: ada/6558: [mainline regression] Wrongly reverted patches Date: Mon, 28 Oct 2002 23:26:00 -0000 [thread overview] Message-ID: <20021029072601.2183.qmail@sources.redhat.com> (raw) The following reply was made to PR ada/6558; it has been noted by GNATS. From: Zack Weinberg <zack@codesourcery.com> To: Nathanael Nerode <neroden@twcny.rr.com> Cc: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, bosch@gcc.gnu.org, jsm28@cam.ac.uk, gcc-bugs@gcc.gnu.org Subject: Re: ada/6558: [mainline regression] Wrongly reverted patches Date: Mon, 28 Oct 2002 23:19:19 -0800 On Tue, Oct 29, 2002 at 02:05:06AM -0500, Nathanael Nerode wrote: > What sort of progress can we make on this? > > Clearly what needs to be checked are the patches to the FSF tree from > 2001 and earlier. But how much earlier ?!? Is there an earlier point > at which we know that the ACT (?) tree had been merged *from* the FSF > tree, so that we don't need to look earlier than that? Otherwise this > is potentially an endless problem. My understanding is that the only patches at issue were those lost when this change occurred: 2002-03-07 Geert Bosch <bosch@gnat.com> * 41intnam.ads, 42intnam.ads, 4aintnam.ads, 4cintnam.ads, 4dintnam.ads, 4gintnam.ads, 4hintnam.ads, 4lintnam.ads, 4mintnam.ads, 4pintnam.ads, 4rintnam.ads, 4sintnam.ads, 4uintnam.ads, 4vcalend.adb, 4zintnam.ads, 52system.ads, 5amastop.adb, 5asystem.ads, 5ataprop.adb, 5atpopsp.adb, 5avxwork.ads, 5bosinte.adb, 5bsystem.ads, 5esystem.ads, [...] utils.c, utils2.c, validsw.adb, xnmake.adb, xr_tabls.adb, xr_tabls.ads, xref_lib.adb, xref_lib.ads : Merge in ACT changes. * 1ssecsta.adb, 1ssecsta.ads, a-chlat9.ads, a-cwila9.ads, g-enblsp.adb, g-md5.adb, g-md5.ads, gnatname.adb, gnatname.ads, mkdir.c, osint-b.adb, osint-b.ads, osint-c.adb, osint-c.ads, osint-l.adb, osint-l.ads, osint-m.adb, osint-m.ads : New files * 3lsoccon.ads, 5qparame.ads, 5qvxwork.ads, 5smastop.adb, 5zparame.ads, gnatmain.adb, gnatmain.ads, gnatpsys.adb : Removed * mdllfile.adb, mdllfile.ads, mdlltool.adb, mdlltool.ads : Renamed to mdll-fil.ad[bs] and mdll-util.ad[bs] * mdll-fil.adb, mdll-fil.ads, mdll-utl.adb, mdll-utl.ads : Renamed from mdllfile.ad[bs] and mdlltool.ad[bs] 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). I am tempted to invoke the patch reversion procedure and demand that this entire merge be backed out. I will certainly do so if the issue is not resolved by the time 3.3 branches. zw
next reply other threads:[~2002-10-29 7:26 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-28 23:26 Zack Weinberg [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 Geert Bosch 2002-10-29 13:06 Nathanael Nerode 2002-10-29 12:56 Nathanael Nerode 2002-10-29 12:46 Nathanael Nerode 2002-10-29 2:36 Joseph S. Myers 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=20021029072601.2183.qmail@sources.redhat.com \ --to=zack@codesourcery.com \ --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).