This is the mail archive of the gcc-patches@gcc.gnu.org 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: [patch] clean up fixincludes math_exception fix


> Here's the revised fixincludes fix to prepare for standard 
> fixincludes on OpenBSD.  OK to commit?

Looks fine.  Likely best to not include fixincl.x diffs in postings, though,
or one has to keep explaining why you must not cvs merge the generated file.

Note to Raja:  doing a merge allows patch (CVS) to think that a certain
part of the patch has been pre-applied when, in fact, a new value is
required.  In other words, merging can cause invisible conflicts with
strange side effects.  The answer to this problem is to cause all merging
to create conflicts and immediate compilation failures.  The only people
who will ever see this problem are those who did a cvs update over a
modified fixincl.x file.  If they modified it once, they can do it again
and regenerate.


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