Highly annoying packaging change from 2.8 -> 2.9

[Martin v. Loewis]

> In fact, all the files moved, but that's not catastrophic.  From the
> point of view of our source management, gcc 2.8.1 had one structure
> and gcc 2.95.2 had another, and the few local changes we had needed to
> be propagated from one file to another.  This sort of thing has
> happened with other packages we build as well; the solution is not, in
> general, to start importing subdirs of the tarfile.

If you need to propagate the changes manually anyway, why can't you
just start with a fresh repository?

Regards,
Martin