[Pkg-clamav-devel] Packaging clamav 0.96

[Michael Tautschnig]

> This one time, at band camp, acab at digitalfuture.it said:
> > Ah something I forgot...
> > Is there anyone here who manages the git commit mail setup?
> > My 1033 commits last night resulted in me, edwin and tomasz being
> > flooded by ban mails (mailman telling us we sent too many emails for the
> > day).
> > Hopefully all the llvm commits are squashed in clamav and I didn't get
> > those people spammed too.
> > 
> > Is this fixxable? If not i'd suggest to squash upstream commits.
> 
> I'd agree with you on squashing commits.  Right now, it's just a pretty
> standard git post hook that looks at all the commits and sends a mail
> from the commit author to the mailing list.  This approach is good
> enough for changes to the debian branch in general, but really isn't
> when we're doing upstream pulls.
> 
> We can either change the git commit hook or change how we commit.  I
> don't mind either way, but the latter seems easier (and possibly more
> correct) to me.
> 
> Thoughts from others?
> 

My git knowledge seems terribly limited in this regard - I had been doing
exactly what was in the receipe I had posted and apparently got squashed
commits; Alberto, at which steps did you deviate? I guess you did the git merge
with --no-squash!?

Best,
Michael

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-clamav-devel/attachments/20100405/db1bc6a2/attachment.pgp>