sm-discuss AT lists.ibiblio.org
Subject: Public SourceMage Discussion List
List archive
- From: David Kowis <dkowis AT shlrm.org>
- To: sm-discuss AT lists.ibiblio.org
- Subject: Re: [SM-Discuss] SCM perforce replacement
- Date: Thu, 16 Mar 2006 08:51:59 -0600
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Maurizio Boriani wrote:
> On 2006-03-16 15:17:08 +0100 Arwed von Merkatz <v.merkatz AT gmx.net>
> wrote:
>
>>> I think this might be of public interest and worth
>>> to put it on the list.
>> Here's my incomplete list:
>> - support for repeated merges between branches (devel->test, ...)
>
> gnuarch does :)
>
Before this gets too much into harping on individual SCM's I'm going to
point out that BearPerson and I had a lengthy discussion over SVN vs
Bazaar-NG. We basically determined that any SCM can be made to do the
things we wanted to do. He had a plan laid out for managing merges and
changes in svn, even though it doesn't really do a good job of merging.
But since branches are cheap in svn, he would create a branch for every
bugfix and then create another branch after the bugfix, then the
differences between those two branches is the changeset that is the bug.
That changeset could then be applied to any other point in the tree.
My point here is, any SCM can be made to do what we want it to do. The
focus will be what does it the easiest, fastest, lowest learning curve,
and is the most stable. So, I'm going to recommend against the simple
"yeah <insert scm here> does that" and instead ask that it's said how
it's done and what steps are involved.
In the svn vs bzr example, there's like 3 or 4 steps to doing a
changeset in svn, but in bzr it's only one or two.
My two cents.
- --
David Kowis
ISO Team Lead - www.sourcemage.org
Source Mage GNU/Linux
Progress isn't made by early risers. It's made by lazy men trying to
find easier ways to do something.
- Robert Heinlein
Any sufficiently advanced technology is indistinguishable from magic.
- Arthur C. Clarke
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
iQGVAwUBRBl7j8nf+vRw63ObAQrqBQv/ZsZgGfGwNbDbt8xPMjTrvEVjDa7X3B5I
/cvMZvyUsv7UjW1urHmcdqYGhwxN2sPZHeWAbdxVdWjrGdXeH6hlinWFkRZDOOYf
368lZipIQgwdCTPllD8dSJ8D3qnyDkrUjX13Ea04q7XsesDAhjbe8Wda+0Buz+pR
+Xh07/lMwvrXWjVYosTGcPZkKP/qhmlzTTVpmPS9ItX3gtVSfyvRdertG8InO4G3
GC3+D/78C2x1j/QxRT/Yxt8y1kece2T5i0AdO9Z0EI/D99MmjgARUbLhmya3GW2Q
PrFN0AqjhsJ30FVcL2Z/ugZzl2r/mdRZscb5BwmchMLZys42V8wtghQrgx5LawA/
8kxuMlpEms6Zo3pjh7ZmqCKT7ER6UJBf4HbWbE121vpGnGlmpSEpFZy/bGMgaGvG
nZk+ZFzb34hWwd+JqH8p+SRPtn678Gt0Ie5C8X7fNu2Z20Na2ZSaZE23fiE3AxFw
BSnQL30J9iIyjPP4mnoYpYctcvkGjSpj
=fUL4
-----END PGP SIGNATURE-----
-
Re: [SM-Discuss] Grimoire Team Lead vote
, (continued)
-
Re: [SM-Discuss] Grimoire Team Lead vote,
Mathieu L., 03/14/2006
-
[SM-Discuss] SCM perforce replacement was: Re: Grimoire Team Lead vote,
Seth Woolley, 03/14/2006
-
Re: [SM-Discuss] SCM perforce replacement was: Re: Grimoire Team Lead vote,
Jeremy Blosser (emrys), 03/14/2006
-
Re: [SM-Discuss] SCM perforce replacement was: Re: Grimoire Team Lead vote,
Seth Woolley, 03/14/2006
-
Re: [SM-Discuss] SCM perforce replacement was: Re: Grimoire Team Lead vote,
Pieter Lenaerts, 03/15/2006
- Re: [SM-Discuss] SCM perforce replacement was: Re: Grimoire Team Lead vote, Arwed von Merkatz, 03/15/2006
- Re: [SM-Discuss] SCM perforce replacement was: Re: Grimoire Team Lead vote, Sergey A. Lipnevich, 03/15/2006
- Re: [SM-Discuss] SCM perforce replacement, Robert Figura, 03/16/2006
- Re: [SM-Discuss] SCM perforce replacement, Arwed von Merkatz, 03/16/2006
- Re: [SM-Discuss] SCM perforce replacement, Maurizio Boriani, 03/16/2006
- Re: [SM-Discuss] SCM perforce replacement, David Kowis, 03/16/2006
- Re: [SM-Discuss] SCM perforce replacement, Karsten Behrmann, 03/16/2006
- Re: [SM-Discuss] SCM perforce replacement, Arwed von Merkatz, 03/16/2006
- Re: [SM-Discuss] SCM perforce replacement, Andrew "ruskie" Levstik, 03/16/2006
- Re: [SM-Discuss] SCM perforce replacement, David Kowis, 03/16/2006
- Re: [SM-Discuss] SCM perforce replacement, Matthew Clark, 03/16/2006
-
Re: [SM-Discuss] SCM perforce replacement was: Re: Grimoire Team Lead vote,
Pieter Lenaerts, 03/15/2006
- Re: [SM-Discuss] SCM perforce replacement, Eric Sandall, 03/20/2006
-
Re: [SM-Discuss] SCM perforce replacement was: Re: Grimoire Team Lead vote,
Seth Woolley, 03/14/2006
- Re: [SM-Discuss] SCM perforce replacement, Maurizio Boriani, 03/16/2006
- Re: [SM-Discuss] SCM perforce replacement, neuron, 03/16/2006
- Re: [SM-Discuss] SCM perforce replacement, Maurizio Boriani, 03/16/2006
-
Re: [SM-Discuss] SCM perforce replacement was: Re: Grimoire Team Lead vote,
Jeremy Blosser (emrys), 03/14/2006
- Re: [SM-Discuss] SCM perforce replacement, Andrew, 03/16/2006
-
[SM-Discuss] SCM perforce replacement was: Re: Grimoire Team Lead vote,
Seth Woolley, 03/14/2006
-
Re: [SM-Discuss] Grimoire Team Lead vote,
Mathieu L., 03/14/2006
Archive powered by MHonArc 2.6.24.