This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: What about providing changes.html in the tarball?

Joseph S. Myers wrote:

Historical reasons; I implemented gennews to avoid the situation of some
news items going in online release notes and others going in NEWS
(renaming the old file to ONEWS), and the old file had been gcc/NEWS; later, the generation was moved into the release script and NEWS removed
from CVS, without changing its location. So simply no-one ever made the
decision to move the file, there were just changes to how it was created.

I see, thanks for the explanation.

Therefore, should we apply something like the below? Would you approve it?

Thanks again,


--- gcc_release	2004-05-20 22:57:35.000000000 +0200
+++ gcc_release.~1.54.~	2004-05-13 10:54:30.000000000 +0200
@@ -232,7 +232,7 @@
     # Regenerate the NEWS file.
-    contrib/gennews > NEWS || \
+    contrib/gennews > gcc/NEWS || \
       error "Could not regenerate NEWS files"
     # Now, we must build the compiler in order to create any generated

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]