-------- Original-Nachricht -------- > Datum: Fri, 22 May 2009 22:46:16 +0300 > Von: Ion-Mihai Tetcu <[email protected]> > An: "SteveB" <[email protected]> > CC: [email protected], [email protected] > Betreff: Re: [Dspam-devel] [Dspam-commit] dspam branch, master, updated. > e8a7e100c6e8e804874ed8c1bad390451de7cad3
> On Fri, 22 May 2009 19:29:08 +0000 > "SteveB" <[email protected]> wrote: > > > This is an automated email from the git hooks/post-receive script. It > > was generated because a ref change was pushed to the repository > > containing the project "dspam". > > > > The branch, master has been updated > > via e8a7e100c6e8e804874ed8c1bad390451de7cad3 (commit) > > from d1680eb967d9f3fa3e36f767585704f16cb471f2 (commit) > > > > Those revisions listed above that are new to this repository have > > not appeared on any other notification email; so we list those > > revisions in full, below. > > > > - Log > > ----------------------------------------------------------------- > > commit e8a7e100c6e8e804874ed8c1bad390451de7cad3 Author: steeeeeveee > > <[email protected]> Date: Fri May 22 21:27:08 2009 +0200 > > > > Fix RBL lookups to produce positive hit for lookups returning > > 127.0.0.X and not just for 127.0.0.2. > > > > ----------------------------------------------------------------------- > > > > Summary of changes: > > src/dspam.c | 4 ++-- > > 1 files changed, 2 insertions(+), 2 deletions(-) > > > > > > hooks/post-receive > > Yay! You're back \o/ > Hallo Ion-Mihai Yes. I am back. I needed to take some time "offline" because of a private issue. But now I am back. +/- at least. I submitted a bunch of patches. I tried to split them up in logical chunks and because of YOU I added everywhere where I could a comment when submitting the patch. So now you should know what I have done :) > I believe some of your commits address bug reports from the tracker? If > so, please add to you commit message > BugID: the_bug_id > so that we can easily who's responsible for fixing what :-) > Also please don't forget to change the status of the respective bug. > > Should this commits be merged down in release branches? > If so, adding: > MFM: X days > will help us remember that. > Alexander already explained me what this MFM is but I still don't get it. MFM = Merge From Master Merge what from master? I am already working with git on the master so what does need to be merged from there again? I don't get it. Explain me as well what the days thing is? Days to wait until the patch is pushed into master (but I am already working on the master with git)? > -- > IOnut - Un^d^dregistered ;) FreeBSD "user" > Steve > "Intellectual Property" is nowhere near as valuable as "Intellect" > FreeBSD committer -> [email protected], PGP Key ID 057E9F8B493A297B -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02 ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ Dspam-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspam-devel
