Skip to Content.
Sympa Menu

sm-discuss - [SM-Discuss] git decision

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Arwed von Merkatz <v.merkatz AT gmx.net>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: [SM-Discuss] git decision
  • Date: Mon, 31 Jul 2006 20:20:39 +0200

Hi everyone,

based on the feedback and the technical merits, my decision is to go for
git and really drop p4 completely. git isn't perfect, but its
scalability is simply amazing compared to every other system I've
tried/used, and it can do everything we want it to do.
As I said before, there are a couple of use-cases that require a little
scripting to make them easier (like integrating a full directory instead
of cherry-picking), but nothing that would really hold us back.
The level of support we've gotten from the people on #git, especially in
the beginning of the evaluation is also something I'm not used to
getting from most projects (smgl is also an exception in that area ;).

That said, I'd like to thank Perforce Software for providing us with a
free license and Tony Smith for providing the perforce server for the
last couple of years. I still think perforce is an amazing SCM, but it
being non-Free, it's not the best option for a Free Software project.

Here are the next steps to do for the final switch:
- we need our current main repository merged with the perforce import.
Jeremy is trying to get that done soon afaik.
- some of the auxiliary repositories like xorg-modular, misc and stuff
need to get their own git repos.
- a few wrapper scripts for stuff that got discussed recently need to be
created. I'll try to find some time for that, but I posted most of my
stuff to this list if anyone wants to create useful scripts from it ;)
- the git guide should get some restructuring. My idea would be to have
a very short, basic guide for common guru use-cases and one or more
longer pages describing some of the backgrounds behind those commands,
especially as they relate to different workflows (e.g. sorcery
development, stable(-rc) grimoire integrator, ...)
- we need a policy about how devel/WIP stuff gets handled in git.
I have some ideas about that, using feature branches, but I haven't
gotten to writing them down in more detail yet. Until the end of this
week I should have a proposal for that ready.

--
Arwed v. Merkatz Source Mage GNU/Linux developer
http://www.sourcemage.org




Archive powered by MHonArc 2.6.24.

Top of Page