how to generate patches out of $DVCS branches: best practices?

[martin f krafft]

also sprach Stefano Zacchiroli <zack at debian.org> [2008.07.15.2031 +0200]:
> I'm a happy (Debian) package maintainer which have just switched
> most of his packages from svn to git. All nice, finally I can work
> directly on a real source code tree instead of fiddling with patch
> management system. Nevertheless, patches are separate in topic
> branches which enable knowing the conceptual changes applied to
> upstream sources.

So that I can remove this thread from my pending list, have you
looked at topgit? I know it's still rough, but I think it's what
you're looking for. topgit's source package has a README.source, and
I'd love comments, especially how to improve the process:

  http://git.debian.org/?p=collab-maint/topgit.git;a=blob;f=debian/README.source;hb=HEAD

-- 
 .''`.   martin f. krafft <madduck at debian.org>
: :'  :  proud Debian developer, author, administrator, and user
`. `'`   http://people.debian.org/~madduck - http://debiansystem.info
  `-  Debian - when you have better things to do than fixing systems
 
"in a country where the sole employer is the state, opposition means
 death by slow starvation. the old principle: who does not work shall
 not eat, has been replaced by a new one: who does not obey shall not
 eat."
                                                 -- leon trotsky, 1937
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature (see http://martin-krafft.net/gpg/)
Url : http://lists.alioth.debian.org/pipermail/vcs-pkg-discuss/attachments/20080923/4a621766/attachment.pgp