We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.
If you want to give it a try, download it from here.
We also code SemanticMerge, and the gmaster Git client.
A few months ago, Linus Torvalds shared some interesting thoughts and concerns regarding the Git branching patterns being used in Kernel development.
Since learning what Torvalds has to say is always enlightening, I wanted to delve into the points he mentioned, because they align pretty closely with the techniques we recommend with Plastic SCM. Obviously, the points apply to Git, Plastic SCM, and any other SCM with good branching support, too.
We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.
If you want to give it a try, download it from here.
We also code SemanticMerge, and the gmaster Git client.
We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.
If you want to give it a try, download it from here.
We also code SemanticMerge, and the gmaster Git client.
This blog post was initially published back in 2008 at DDJ but since DDJ "Guru blogs" moved to the new location some images have been broken so I've decided to publish it again here.
We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.
If you want to give it a try, download it from here.
We also code SemanticMerge, and the gmaster Git client.
This is based upon a real story: I have a piece of code that launches an external application, but it wasn’t taking into account the possibility of having programs with spaces in their pathnames. Something like c:\mypath\tool.exe worked, but not something like c:\program files\my tool\tool.exe. To be able to launch such programs, we need to enclose the pathnames in quotes.
The original code was something like the following and obviously unable to deal with quotes:
We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.
If you want to give it a try, download it from here.
We also code SemanticMerge, and the gmaster Git client.
Edit Jan 10th 2018: Brad Appleton (of SCM fame), contributed a comment adding more info about Aide de Camp, about the first version controls available for PC(DOS) and highlighting that task branches are not the same as feature branches, something we try to stress on all our communication but failed to do here :-)
It is also worth to note that we have a specific site for version control history.
Edit Feb 12th 2014:We just collected all the comments and suggestions from readers and created a dedicated site with a bigger number of version controls here. Enjoy :P
Software Configuration Management (or source code management, for you real hard core coders) has been around for quite a few years, slowly moving from an almost manual-labor, dark prehistory to the shiny days of the DVCS (distributed version control system).
You've all used at least one of the SCMs on the following list, but are you aware of how long the system you're using has been around? Do you know the big names? Ok, that's what I'll try to supply with this short compilation.
We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.
If you want to give it a try, download it from here.
We also code SemanticMerge, and the gmaster Git client.
$ mono Instrument.exe --help
Usage: Instrument [OPTIONS] assemblies
Instrument one or more assemblies to
record profiling data.
If only one assembly is specified,
instrumented assembly output name and
data filename can be set. Otherwise
defaults are chosen for each assembly.
Options:
-v, --verbose Increase verbosity
-h, -?, --help Show this message and exit
-f, --filename=VALUE The filename where profiling data is written to
at runtime
-o, --out=VALUE The filename where the instrumented assembly is
written
-p, --private Include private types
-c, --class=VALUE The specific class to instrument (can be given
more than once)
$ ls -l hello.* Concerto*dll *.mprof
-rwxr-xr-x. 1 dick dick 13312 2010-11-08 14:06 Concerto.dll
-rw-r--r--. 1 dick dick 384 2010-11-04 20:10 hello.cs
-rwxr-xr-x. 1 dick dick 3072 2010-11-05 16:51 hello.exe
$ mono Instrument.exe -vvv hello.exe
Instrumenting hello.exe, creating hello.exe.ins
The helper assembly is Concerto-hello_exe.dll
Data shall be written to concerto-hello_exe.mprof
Instrumenting class hello
Instrumenting method System.Void hello::.ctor()
Instrumenting method System.Int32 hello::DoStuff(System.Int32)
Instrumenting method System.Void hello::DoMoreStuff()
Instrumenting method System.Void hello::Main()
Done.
$ ls -l hello.* Concerto*dll
-rw-r--r--. 1 dick dick 13824 2010-11-12 11:53 Concerto-hello_exe.dll
-rwxr-xr-x. 1 dick dick 13312 2010-11-08 14:06 Concerto.dll
-rw-r--r--. 1 dick dick 384 2010-11-04 20:10 hello.cs
-rwxr-xr-x. 1 dick dick 3072 2010-11-05 16:51 hello.exe
-rw-r--r--. 1 dick dick 3584 2010-11-12 11:53 hello.exe.ins
$ mono hello.exe.ins
Hello, world!
1
1
2
$ ls -l hello.* Concerto*dll *.mprof
-rw-r--r--. 1 dick dick 13824 2010-11-12 11:53 Concerto-hello_exe.dll
-rwxr-xr-x. 1 dick dick 13312 2010-11-08 14:06 Concerto.dll
-rw-r--r--. 1 dick dick 365 2010-11-12 11:54 concerto-hello_exe.mprof
-rw-r--r--. 1 dick dick 384 2010-11-04 20:10 hello.cs
-rwxr-xr-x. 1 dick dick 3072 2010-11-05 16:51 hello.exe
-rw-r--r--. 1 dick dick 3584 2010-11-12 11:53 hello.exe.ins
$ mono mprof-decoder.exe concerto-hello_exe.mprof
------------------------------------------------
Reporting execution time (on 4 methods)
97.19% (0.007282s) hello.System.Void hello::Main()
2.48% (0.000186s) hello.System.Int32 hello::DoStuff(System.Int32)
1 calls from hello.System.Void hello::Main()
1 calls from hello.System.Void hello::DoMoreStuff()
0.33% (0.000025s) hello.System.Void hello::DoMoreStuff()
1 calls from hello.System.Void hello::Main()
------------------------------------------------
Reporting execution time by stack frame
97.19% (0.007282s, 1 calls) hello.System.Void hello::Main()
2.33% (0.000169s, 1 calls) hello.System.Int32 hello::DoStuff(System.Int32)
0.34% (0.000025s, 1 calls) hello.System.Void hello::DoMoreStuff()
66.67% (0.000017s, 1 calls) hello.System.Int32 hello::DoStuff(System.Int32)
$ mono Instrument.exe -vv plastictcpchannel.dll
Instrumenting plastictcpchannel.dll, creating plastictcpchannel.dll.ins
The helper assembly is Concerto-plastictcpchannel_dll.dll
Data shall be written to concerto-plastictcpchannel_dll.mprof
Instrumenting class Codice.Channels.ClientSinkProvider
Instrumenting class Codice.Channels.ClientSink
Instrumenting class Codice.Channels.PlasticBinaryServerFormatterSink
Instrumenting class Codice.Channels.PlasticBinaryServerFormatterSinkProvider
Instrumenting class Codice.Channels.PlasticTcpChannel
Done.
$ mono Instrument.exe -vv -c
Codice.Channels.PlasticBinaryServerFormatterSinkProvider -c
Codice.Channels.ClientSinkProvider plastictcpchannel.dll
Instrumenting plastictcpchannel.dll, creating plastictcpchannel.dll.ins
The helper assembly is Concerto-plastictcpchannel_dll.dll
Data shall be written to concerto-plastictcpchannel_dll.mprof
Instrumenting class Codice.Channels.ClientSinkProvider
Instrumenting class Codice.Channels.PlasticBinaryServerFormatterSinkProvider
Done.
We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.
If you want to give it a try, download it from here.
We also code SemanticMerge, and the gmaster Git client.
It's been a week since we announced the Community Edition and a big number of developers have already downloaded and started to work with Plastic.
We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.
If you want to give it a try, download it from here.
We also code SemanticMerge, and the gmaster Git client.
We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.
If you want to give it a try, download it from here.
We also code SemanticMerge, and the gmaster Git client.
We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.
If you want to give it a try, download it from here.
We also code SemanticMerge, and the gmaster Git client.
We're just announcing a Community Edition of Plastic SCM. We will license Plastic SCM for free to environments with up to 15 developers, which will cover a huge percentage of the development teams.
17 comentarios: