git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carl Worth <cworth@cworth.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Theodore Tso <tytso@mit.edu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	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, 01 Aug 2007 08:49:46 -0700	[thread overview]
Message-ID: <87tzrjfe5h.wl%cworth@cworth.org> (raw)
In-Reply-To: <7vr6mn5znm.fsf@assigned-by-dhcp.cox.net>

[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]

On Wed, 01 Aug 2007 03:15:25 -0700, Junio C Hamano wrote:
>
> Are you suggesting to make -l the default for local, in other
> words?  I personally do not make local clone often enough that I
> am not disturbed having to type extra " -l" on the command line.

Personally, I think it would be a great default.

And I think the frequency with which you type this command is not a
good metric for deciding if a command-line option should be required.

Instead, the focus should be on having good defaults for a good user
experience, (for example, the benchmarking that started this thread
that gave a bad first impression of git).

So, just making git-clone go as fast as possible when local, without
requiring any additional options from the user, would be a very good
thing.

As for the concern that new users might do local clones in the hope to
get some redundancy, hopefully the fact that the operation is
instantaneous will give plenty of clue to the user that no redundancy
has been provided. That should be enough to send the user looking for
the documentation to find the --no-hard-links option.

-Carl

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-08-01 16:27 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 [this message]
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
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=87tzrjfe5h.wl%cworth@cworth.org \
    --to=cworth@cworth.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --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).