[development] git main branch - how to use it, or not use it

Arlin Sandbulte arlinsandbulte at gmail.com
Tue Mar 1 19:25:00 UTC 2011

There is a lot of discussion and ideas about git work flows right now.
It will probably take some time for best practices to evolve and gain
acceptance on d.o

Regarding the main branch, others have said it seems pretty useless when a
release (dev in particular) cannot be attached to it anyway.
I think the only thing 'special' about main is that it is the default
checked out branch when cloning a repository.
So, what to do with it...

I like the way the rules project seems to be handling it:
Just have a readme on the main branch noting that all files are located on
other branches and all work should be done there.  (Even though this might
be a carryover from the good ole CVS days.)
Any other suggestions or words of wisdom?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20110301/97e7a155/attachment.html 

More information about the development mailing list