Re: [Sketch-devel] drowning in patches

[Bernhard R. <ber...@in...>]

On Thu, Dec 13, 2001 at 03:47:38AM -0800, Mark Rose wrote:
> I have a mess of small patches to send you as I get them
> sorted out.  As you have a lot more experience dealing with
> a large project, do you have any suggestions for keeping
> things organized? =20

If you want my advice on the topic, too, read on here it comes.

First, if you don't know it already, the Software Release Practice HOWTO
contains some general hints on how to send patches.
  http://www.linuxdoc.org/HOWTO/Software-Release-Practice-HOWTO/patching.ht=
ml

You already know all this, but it is a nice writeup.
I would suggest you use diff -u for patches.

Let me add more general rules:

* You have to make it easy for the maintainer of sketch (Bernhard Herzog)
  to include the patches.

* Keep another fresh copy of the latest release or cvs version
	you are working on around. Thus if you have something which
	can be seperated as a small patch, you can test it more=20
	easily.

* CVS can direcly spit out the changes to the repository and also
	lets you use the -u flag to diff.

* If you publish your patches in the open, make sure that people=20
excatly know on which version they should be applied.


Hope that help to make your well appreciated efforts to sketch even smoothe=
r,

Best,
Bernhard R.


--=20
Professional Service around Free Software                (intevation.net) =
=20

If sketch is useful for you, consider tipping the project:
               http://sketch.sourceforge.net/payments.html