Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Erik de Castro Lopo <ocaml-erikd@mega-nerd.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] [OT] Rant about VCS: Conclusions
Date: Wed, 22 Dec 2004 09:36:27 +1100	[thread overview]
Message-ID: <20041222093627.5a5376a3.ocaml-erikd@mega-nerd.com> (raw)
In-Reply-To: <41C89DB2.4020105@orcaware.com>

On Tue, 21 Dec 2004 14:03:30 -0800
Blair Zajac <blair@orcaware.com> wrote:

> Regarding merging, unlike CVS, Subversion has changesets, so merging is 
> simply picking the changeset(s) you want from one path and applying it 
> to another:

Ahh, now I remember the problem subversion has with merging across 
branches with respect to Arch.

Please correct me if I am wrong, but from what I have heard, 
subversion is not able to recognise if a changeset has already
been applied or not and trying to apply a changeset which has
already been applied can lead to merge conflicts which need 
manual intervention to correct.

Arch OTOH keeps a log of all changesets applied to a tree. That 
means that if you have three branches A, B and C, all with the same
common ancestor you can merge A -> B and then B -> C. Now if you
try to merge A -> C Arch is clever enough to figure out which
changesets in A have already been applied to C and which ones 
haven't, and then only apply the ones that have not been applied.


Erik
-- 
+-----------------------------------------------------------+
  Erik de Castro Lopo  nospam@mega-nerd.com (Yes it's valid)
+-----------------------------------------------------------+
I have found that good programmers either do not make the kind
of mistakes that Ada can prevent, or insert enough checks that
they catch those mistakes about as efficiently as an Ada
environment can. At that point, the use of Ada gives no further
productivity advantage.


  reply	other threads:[~2004-12-21 22:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-17 17:07 [OT] Rant about VCS Alex Baretta
2004-12-17 18:42 ` [Caml-list] " Paul Snively
2004-12-17 19:28   ` Yaron Minsky
2004-12-17 20:13   ` Erik de Castro Lopo
2004-12-17 21:37 ` Sven Luther
2004-12-17 22:27   ` Erik de Castro Lopo
2004-12-18  9:28     ` Sven Luther
2004-12-18  9:49       ` Erik de Castro Lopo
2004-12-18 14:45         ` Sven Luther
2004-12-18 20:03           ` Erik de Castro Lopo
2004-12-18  9:52       ` Erik de Castro Lopo
2004-12-18 14:45         ` Sven Luther
2004-12-18 11:24       ` Richard Jones
2004-12-18 15:01         ` Sven Luther
2004-12-18 15:22           ` Richard W.M. Jones
2004-12-18 15:35             ` Richard W.M. Jones
2004-12-18 15:39             ` Sven Luther
2004-12-21  9:07     ` [Caml-list] [OT] Rant about VCS: Conclusions Alex Baretta
2004-12-21 22:03       ` Blair Zajac
2004-12-21 22:36         ` Erik de Castro Lopo [this message]
2004-12-21 23:19           ` David Brown
2004-12-21 23:47             ` Erik de Castro Lopo
2004-12-18  0:48 ` [Caml-list] [OT] Rant about VCS skaller
2004-12-18 11:25 ` henri dubois-ferriere
2004-12-18 15:03   ` Sven Luther

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041222093627.5a5376a3.ocaml-erikd@mega-nerd.com \
    --to=ocaml-erikd@mega-nerd.com \
    --cc=caml-list@yquem.inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox