From: "Jakub Narębski" <jnareb@gmail.com>
To: "Igor Djordjevic" <igor.d.djordjevic@gmail.com>,
"Michael Hüttermann" <michael@huettermann.net>,
git@vger.kernel.org
Subject: Re: Reference for quote "creating branch is not the issue, merging is", in context of Subversion/Git
Date: Mon, 27 Feb 2017 23:42:01 +0100 [thread overview]
Message-ID: <a3960248-46c1-b814-13ef-cf8c0435be9a@gmail.com> (raw)
In-Reply-To: <32232f89-a6f8-be30-278a-bdfedae0716a@gmail.com>
W dniu 26.02.2017 o 16:19, Igor Djordjevic pisze:
> Hello Michael,
>
> On 26/02/2017 12:40, Michael Hüttermann wrote:
>> Linus Torvalds made a statement regarding merging/branching and stated
>> (as far as I know) that "creating branch is not the issue, merge is", in
>> context of Subversion/Git.
>> I do not find the origin source for that. Can you please help and point
>> me to a statement or article where Linus elaborated on this?
>
> Could it be that you think of "Tech Talk: Linus Torvalds on Git"[1]
> (held on May 3, 2007)?
>
> To give you some clue, here`s an excerpt from Linus' talk/presentation
> (taken from the transcript[2] containing the whole thing):
>
> "... Subversion for example, talks very loudly about how they do CVS
> right by making branching really cheap. It's probably on their main
> webpage where they probably say branching in subversion is O(1)
> operation, you can do as many cheap branches as you want. Nevermind
> that O(1) is actually with pretty large O I think, but even if it
> takes a millionth of a second to do branching, who cares? It's the
> wrong thing you are measuring. Nobody is interested in branching,
> branches are completely useless unless you merge them, and CVS cannot
> merge anything at all. You can merge things once, but because CVS
> then forgets what you did, you can never ever merge anything again
> without getting horrible horrible conflicts. Merging in subversion is
> a complete disaster. The subversion people kind of acknowledge this
> and they have a plan, and their plan sucks too. It is incredible how
> stupid these people are. They've been looking at the wrong problem
> all the time. Branching is not the issue, merging is..."
>
> This specific branch/merge performance talk starts at 50:20[3], where
> the part quoted above comes at 51:34[4].
Note also that while "creating branch is not the issue, merge is"
remains true, modern Subversion (post 1.5) makes merging easy thanks
to svn:mergeinfo property.
Though it does it in completely different way than Git and other
"graph of commits" VCS-es, because of the "branch is directory"
philosophy, namely that it keeps information about what was merged
in, rather than finding common ancestor(s) and using this information
for resolving merge.
>
> Please note that there`s more context before and after this excerpt
> that puts it all into the meant perspective, so you may really want
> to watch/listen/read the whole thing anyway.
>
> Regards,
> Buga
>
> [1] https://www.youtube.com/watch?v=4XpnKHJAok8
> [2] https://git.wiki.kernel.org/index.php/LinusTalk200705Transcript
> [3] https://youtu.be/4XpnKHJAok8?t=3020
> [4] https://youtu.be/4XpnKHJAok8?t=3094
>
prev parent reply other threads:[~2017-02-27 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 11:40 Reference for quote "creating branch is not the issue, merging is", in context of Subversion/Git Michael Hüttermann
2017-02-26 15:19 ` Igor Djordjevic
2017-02-27 22:42 ` Jakub Narębski [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a3960248-46c1-b814-13ef-cf8c0435be9a@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=igor.d.djordjevic@gmail.com \
--cc=michael@huettermann.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).