weblog.masukomi.org

Put Up or Shut Up (Take 2) September 4, 2007

Put Up or Shut Up (take 2)



You probably saw that I spent the beginning of this weekend whipping up a tool
to synchronize a distributed system with Perforce. Well, I got to thinking, and
thinking leads to refactoring, and unit testing, and bug fixing, and TONS OF NEW
FEATURES. So many in fact that I’ve given it an entirely new name.



Introducing:
SSCM

Catchy name huh? It stands for Simultaneous Source Control Managers (manager)
and it enables you to easily keep any combination of Subversion, Perforce,
Mercurial (Hg), Git, and Darcs synced, tag all their repos simultaneously, and
do quick commits to all of them (except Perforce).



Why would you want such a thing?

• Your employer requires you to use a standard centralized SCM like Subversion
  or Perforce and you’d like to take advantage of a Distributed Source Control
  Manager like 
  Mercurial (hg),
  Git, or 
  Darcs without having to duplicate all
  your adds, commits, and so forth for the distributed system and the system
  everyone else at your company is using.
  
• You manage an open source program and would like to reach the largest
  possible audience by offering its source code via a variety of SCMs at the
  same time. Or, maybe you just can’t decide on a single distributed system.

It’s free, it works, it’s got a helpful
README and
plenty
of API docs to boot.



Side note: This should not be considered a substitute for learning how to
actually use the SCMs you  want to manage with it. Although if you know one
it’ll get you the basic operations in the other ones you add while you’re still
learning them.

Popularity: 2% [?]