Introductory mail

[martin f krafft]

also sprach Manoj Srivastava <srivasta at acm.org> [2008.09.29.1745 +0200]:
>         I don't really want to add ./debian/patches directory to keep
>  track of previous patch series;

Well, it is the only truly-accepted, VCS-agnostic way to have
a patch series in a Debian package, so why not?

> and I think we should perhaps add a possibility for topgit to
> generate patch series based on a tag. Then, you tag all topic--
> branches when releasing, and then would be able to extract the
> patches corresponding to the tag(s) at any time in the future.

This is going to get ugly, since for every tag on the build branch,
you need to create two tags on each topgit branch, denoting the
begin and end of the feature branch (which is done with
refs/top-bases/$name and refs/heads/$name (the tip) right now).

You might be able to determine either of these from the DAG, but
I somehow doubt it. I'd love to be proven wrong.

-- 
 .''`.   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
 
"by accepting this brick through your window, you accept it as is
 and agree to my disclaimer of all warranties, express or implied,
 as well as disclaimers of all liability, direct, indirect,
 consequential or incidental, that may arise from the installation
 of this brick into your building."                 -- seen on irc
-------------- 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/20080929/cf325f84/attachment.pgp