git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Allan Wind <allan_wind@lifeintegrity.com>
Cc: Theodore Tso <tytso@mit.edu>, Junio C Hamano <gitster@pobox.com>,
	Jakub Narebski <jnareb@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Git benchmark - comparison with Bazaar, Darcs, Git and Mercurial
Date: Wed, 1 Aug 2007 21:13:16 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.0.999.0708012109040.3582@woody.linux-foundation.org> (raw)
In-Reply-To: <20070802040201.GI23484@lifeintegrity.com>



On Thu, 2 Aug 2007, Allan Wind wrote:
> 
> I would expect /something and file:///something to behave exactly the 
> same way (the latter just having bit extra syntax sugar).

I do agree that they should be basically the same, but from an 
implementation standpoint it actually makes a lot of sense to separate 
them. Also, there's actually a small amount of "logic" in it: the 
/something is obviously a "raw filename", while the "file:://something" 
clearly is something a lot more abstract.

I don't actually have a very strong opinion, but I do think that "file://" 
makes sense regardless (ie the patch I sent out is probably a good idea).

I also strongly dispute that "file://something" is _identical_ to just 
"something". There's a huge difference, as anybody who has ever tried to 
do

	cp file://file-A file-B

will have hopefully found out. They may mean the same thing, but they have 
totally different levels of abstraction, so it does actually make some 
sense that you end up *cloning* the same thing, but different ways.

		Linus

  reply	other threads:[~2007-08-02  4:14 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01  0:16 Git benchmark - comparison with Bazaar, Darcs, Git and Mercurial Jakub Narebski
2007-08-01  2:14 ` Linus Torvalds
2007-08-01  5:50   ` Junio C Hamano
2007-08-01  8:48     ` David Kastrup
2007-08-01  9:24     ` Theodore Tso
2007-08-01 10:15       ` Junio C Hamano
2007-08-01 13:20         ` Alex Riesen
2007-08-01 13:20           ` Alex Riesen
2007-08-01 13:23             ` Alex Riesen
2007-08-01 15:49         ` Carl Worth
2007-08-01 17:03           ` Linus Torvalds
2007-08-01 18:17             ` David Kastrup
2007-08-01 20:36               ` Florian Weimer
2007-08-02  6:09             ` Junio C Hamano
2007-08-02 10:29               ` David Kastrup
2007-08-03  0:51                 ` Junio C Hamano
2007-08-03  6:14                   ` David Kastrup
2007-08-03  8:20                   ` Johan Herland
2007-08-01 22:03         ` Theodore Tso
2007-08-01 22:49           ` Brandon Casey
2007-08-02  4:02           ` Allan Wind
2007-08-02  4:13             ` Linus Torvalds [this message]
2007-08-01 22:18         ` Jakub Narebski
2007-08-02 11:19           ` Jakub Narebski
2007-08-02 18:08         ` Ramsay Jones
2007-08-01  8:33   ` Jakub Narebski
2007-08-01  8:48     ` Junio C Hamano
2007-08-01 23:51       ` Jakub Narebski
2007-08-01  2:17 ` Shawn O. Pearce

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=alpine.LFD.0.999.0708012109040.3582@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=allan_wind@lifeintegrity.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).