[Pkg-clamav-devel] repo set up

[Michael Tautschnig]

[...]
> 
> My idea of workflow is to clone the group repository and add the read
> only clamav-devel as a remote.  When doing a new version release, it
> should be possible to just pull the HEAD of the relevant upstream branch
> (upstream/0.93, currently).  When security or other issues arise, it
> should be possible to just cherry-pick a commit from upstream HEAD,
> which we see as master - in that case, just update master from the
> remote and then cherry-pick into the appropriate distro branch(es).
> 
[...]

Just one unmentioned workflow: Local bugfixing - am I right that this happens in
the debian/unstable branch?

What about commit-mails? Are these set up, or should they be enabled for
specific users instead of sending commits to the list?

Best,
Michael

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-clamav-devel/attachments/20080903/6dc2a559/attachment.pgp