Some point about your GIT usage, since you seem to be learning about GIT
as well.
- why did you create a new pristine tree, in stead of forking an
existing tree? If you fork an existing tree it is trivial to rebase your
tree agains for example mine, and thereby keep track of 'upstream' changes.
- you're including massive amounts of cruft in your tree; binary files,
files generated by automake, autoconf and libtool, etc.
- your changesets are way too large. Commit more often, so the actual
changes can be tracked. Don't make me wade through changesets of
hundreds of lines (mostly cruft) just to find the actual code changes.
- if you commit changes give them a descriptive message. 'push' is no
message at all.
--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin
* Premium Hosting Services and Web Application Consultancy *
www.nfg.nl/i...@nfg.nl/+31.85.877.99.97
________________________________________________________________
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
