[Mono-dev] Git faq updated with workflows

[pablosantosluac at terra.es]

Hi all,

I've just posted a very detailed entry describing "branch per task".

http://codicesoftware.blogspot.com/2010/08/branch-per-task-workflow-explained.html

I didn't specifically talk about Plastic so it's perfectly doable with
Git too.

pablo

On 29/07/2010 13:17, pablosantosluac at terra.es wrote:
> All,
> 
> I'd strongly recommend you separate every task (every entry on bugzilla)
> on a separated branch.
> 
> I'm very used to it since this is the way we work internally in Plastic
> (and what we do recommend to all our customers). It gives you perfect
> traceability and flexibility to handle all changes.
> 
> Git is perfectly capable of handling high number of branches (as plastic
> is too, something you didn't have with SVN), so I think this one is a
> perfect solution.
> 
> Basically it means: you'll be using branches instead of "commits" as
> "unit of change".
> 
> Hope it helps,
> 
> pablo
> 
> On 29/07/2010 3:52, Andreia Gaita wrote:
>> I've added a couple of simple workflows to our git faq,
>> http://www.mono-project.com/GitFAQ#Workflow . See if these work for
>> you, they should make it easier to avoid merge commits. There are
>> plenty of ways to do things, and these don't include working on forks,
>> although it's not too different. More to come later, opinions welcome.
>>
>> andreia gaita
>> _______________________________________________
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>