Excerpts from Sylvain Le Gall's message of Wed Jan 30 14:58:21 +0100 2008: > On 30-01-2008, Nicolas Pouillard wrote: > > > > --===============1976516885== > > Content-Type: multipart/signed; protocol="application/pgp-signature"; > > boundary="=-1201694054-349540-27517-1921-14-="; micalg="pgp-sha1" > > > > > > --=-1201694054-349540-27517-1921-14-= > > Content-Type: text/plain; charset=UTF-8 > > > > Excerpts from daniel.buenzli's message of Wed Jan 30 12:15:03 +0100 2008: > >> > >> Le 30 janv. 08 à 11:50, Nicolas Pouillard a écrit : > >> > >> > And what if the author of P_{i1} have changed it's project > >> > (locally or not), > >> > let's say some file renamings, adding some code around the > >> > bug, do some > >> > global replacing... > >> > > >> > With such a diff file you end-up with a patch that is not applicable. > >> > > >> > That's not a problem when using darcs! > >> > >> The port system should focus on making it easy to use and share ocaml > >> modules, not helping to develop them. If you want to help in the > >> development of a module interact directly with the project's vcs. > > > > Of course you want to contribute to upstream. But I don't want to wait them, > > so we need to modify them in a coherent way. > > > > Upstream should be the synchronization point. Because, if you make it > move (by sending him patches), the benefit of your patches will also go > into other distribution (GODI/Fedora/Debian). Debian try to push patches > to upstream because it makes other get the benefit from it... Of course, you send the patch upstream, then you don't want to wait for them to answer in order to continue your task. -- Nicolas Pouillard aka Ertai