Alan Coopersmith wrote: > 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.
Wasn't it on the webserver, too ? > 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. Unfortunately that won't work for OS/Net since (AFAIK) runtime patching of sources is not allowed and the *.diff stretches over the Makefile parts, too. And this wasn't the goal for the *.diff idea either. The *.diff is there to have a quick&&efficient way to toggle between the patched and unpatched codebase on demand for both updates and testing, as a help for those who work and maintain the code. It's something needed to organise ourselves in some usefull way. ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;)
