Roland Mainz wrote:
> Oh, that's a "great idea". Small example:
> Once upon the time someone wrote a IPv6 patch for dtksh, a test suite
> for the change and some documentation. The test suite and documentation
> were not put back into the normal codebase and were stored "elsewhere"
> in a "permanent storage which will not go away".
No, it was stored in the engineer's home directory, which was a mistake.
As for the *.diffs, the way we handle this in projects which expect to
update to upstream sources often is to only store the diffs, and not
check in the sources with the diffs applied - that also encourages
engineers to submit fixes upstream so that the diffs don't have to be
updated every time a new upstream release comes out.
(We used to keep X sources the old way, checking in the original source,
and our mods on top of it, and in fact, still do for the X11R6-based
bits in /usr/openwin that we haven't replaced yet - it is much more
painful to keep up-to-date than just keeping a diff you apply with gpatch
to the latest upstream tarballs.)
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
