From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
git@vger.kernel.org,
James Bottomley <James.Bottomley@SteelEye.com>
Subject: Re: Handling renames.
Date: Thu, 14 Apr 2005 11:49:17 -0700 [thread overview]
Message-ID: <425EBB2D.3060508@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0504141145220.7211@ppc970.osdl.org>
Linus Torvalds wrote:
>
> On Thu, 14 Apr 2005, H. Peter Anvin wrote:
>
>>Although Linus is correct in that an SCM doesn't *have* to handle this,
>>it really feels like shooting for mediocracy to me. We might as well
>>design it right from the beginning.
>
> No. git is not an SCM. it's a filesystem designed to _host_ an SCM, and
> that _is_ doing it right from the beginning.
>
> Keep the abstractions clean. Do _not_ get confused into thinking that git
> is an SCM. If you think of it that way, you'll end up with crap you can't
> think about.
>
> And at a filesystem layer, "rename" already exists. It's moving an object
> to a new name in a tree. git already does that very well, thank you very
> much.
>
> But a filesystem rename is _not_ the same thing as an SCM rename. An SCM
> rename is built on top of a filesystem rename, but it has its own issues
> that may or may not make sense for the filesystem.
>
I wasn't referring to git per se, I was referring to the hosted SCM.
-hpa
next prev parent reply other threads:[~2005-04-14 18:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 17:54 Handling renames David Woodhouse
2005-04-14 18:11 ` Linus Torvalds
2005-04-14 19:09 ` David Woodhouse
2005-04-14 18:12 ` Ingo Molnar
2005-04-14 18:32 ` Linus Torvalds
2005-04-14 18:58 ` Ingo Molnar
2005-04-14 19:20 ` David Woodhouse
2005-04-14 19:21 ` David Mansfield
2005-04-14 18:21 ` H. Peter Anvin
2005-04-14 18:48 ` Linus Torvalds
2005-04-14 18:49 ` H. Peter Anvin [this message]
2005-04-14 19:22 ` Zach Welch
2005-04-14 19:40 ` Andrew Timberlake-Newell
2005-04-14 20:42 ` Naming the SCM (was Re: Handling renames.) Steven Cole
2005-04-14 20:53 ` Petr Baudis
2005-04-14 20:58 ` H. Peter Anvin
2005-04-14 21:01 ` Petr Baudis
2005-04-14 23:17 ` Peter Williams
2005-04-14 22:23 ` Handling renames Daniel Barkalow
2005-04-14 22:46 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2005-04-15 13:37 linux
2005-04-15 13:53 ` David Woodhouse
2005-10-21 23:40 git-rev-list: add "--dense" flag Linus Torvalds
2005-10-22 0:37 ` Petr Baudis
2005-10-22 0:47 ` Handling renames Petr Baudis
2005-10-22 1:28 ` Linus Torvalds
2005-10-22 1:51 ` Petr Baudis
2005-10-22 2:10 ` Junio C Hamano
2005-10-22 2:49 ` Petr Baudis
2005-10-22 3:23 ` Linus Torvalds
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=425EBB2D.3060508@zytor.com \
--to=hpa@zytor.com \
--cc=James.Bottomley@SteelEye.com \
--cc=dwmw2@infradead.org \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.