Q: How-To Submit patches

[Martin Albert <MartinAlbert@gmx.net>]

Hello!

I'm looking for info/doc/scripts/hints on proper / practical ways to
submit patches.

Of interest to me is also the proper way to generate a patch to a
single file - what is the best point in the dir structure to start?
Toplevel, ../Toplevel, ... ?

But currently i do have fixes for around 15 reported bugs on three pkgs.
I don't know how to generate the patch (same q as above) nor do i think
it is practical to submit them to each bug.

I now built a private source pkgs (which could well become NMUs, for
some bugs are release critical and quite old), which has the advantage
that it keeps all my changes, also to the .orig, together, but it
doesn't clearly point to where sth. actually changed.

I hope someone might be willing to point me in the right direction.

btw. any place anything about practical usage of apt-cache. That thing
drives me crazy. I know what it knows, what i want, but i don't get it
to tell me. Most important: i have to track stable, testing & unstable
and want to know the newest _source_.

greetings, martin