On Tue, 11 Dec 2012 19:43:55 +0100 Togan Muftuoglu <[email protected]> wrote:
> On 12/11/2012 07:38 PM, parafin wrote: > > On Tue, 11 Dec 2012 19:19:42 +0100 > >> Maybe a better solution, just a thought, is to follow a structure as > >> outlined in <http://nvie.com/posts/a-successful-git-branching-model/> > >> > >> This approch could help us solve the versioning issues for us,the > >> nightly package builders > > > > There's nothing in there about patch releases so what's exactly you're > > proposing? Just don't do them? Or always release git master? That won't > > work for us. > > > > Look at the release and hotfix branch approch I'm looking at them. Their approach is different from ours, changing development process just because of version numbering issues sounds stupid, I don't see any need for this. > > PS. Do not put me in CC or TO please just reply to the mailing list > > Togan > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > darktable-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/darktable-devel ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
