Regarding git branching model, I read these two howtos:
http://nvie.com/posts/a-successful-git-branching-model/ This document is pretty much thought out, and I guess it really covers the development/release processes of log4php. I would use it as a reference. Since now, I was using lightweight tags, but document recommends using annotated tags with -a option. For this kind of project that log4php is, annotated tags are more suitable. So +1 from me, for this model. https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/working-with-git/ Even though, the first document doesn't cover too much, there is really interesting passage about rebasing multiple commits. On Sun, Dec 2, 2012 at 4:58 PM, Ivan Habunek <ivan.habu...@gmail.com> wrote: > On 30 November 2012 17:07, Vladimír Gorej <go...@codescale.net> wrote: > > I did not find any problems with the repo, except already known problem > with > > the duplicate tags. I reviewed some of the history commits with 'git gui' > > tool and everything seemed fine. > > Yeah, i did the same using tortoise-git, and all seems well. > > > Maybe we should have a look at this: > > https://help.github.com/articles/dealing-with-line-endings#platform-all, > if > > commiters/contributors develop on various platforms. > > Well, the plan was to start using PSR-2 coding standard, and it says > that all files should use unix-style line breaks (LF) regardless of > the platform. > > So the simplest solution is to put the following line in .gitattributes: > * text eol=lf > > That way all line breaks will be converted to LF. > > Regards, > Ivan > -- Vladimír Gorej | CodeScale s.r.o. email: go...@codescale.net tel: +420 777 861 279, +421 948 023 011 web: http://www.codescale.net
