> This one time, at band camp, [email protected] 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
pgp7La45F8Lm6.pgp
Description: PGP signature
_______________________________________________ Pkg-clamav-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-clamav-devel
