Subject: Re: [boost] [git help] Documenting common modular boost workflows
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2013-10-22 11:26:57
On Mon, Oct 21, 2013 at 6:56 PM, Niall Douglas <s_sourceforge_at_[hidden]>wrote:
> I think that topic - how do we extend git flow the process to cope
> with Boost modularisation - is where we should be focusing our
> attention, not on git flow the tool, git flow the process for a
> single repo, whether we agreed on git flow, whether git flow is good
> or bad etc.
Although I would like to see a short and simple explanation of the basic
gitflow process also. As it helps in understanding and translating to
whatever git tool you happen to be using.
> Once agreed, then we know how to extend git flow the tool usefully.
> And possibly TortoiseGit too.
Although I exclusive use the Exclipse git integration (as I can't bear to
use the low contextual information git CLI).
-- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk