git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Simon Richter <Simon.Richter@hogyros.de>,
	Pavel Roskin <proski@gnu.org>, git <git@vger.kernel.org>
Subject: Re: Getting rid of symlinks in .git?
Date: Fri, 11 Nov 2005 16:05:30 +0100	[thread overview]
Message-ID: <20051111150530.GT30496@pasky.or.cz> (raw)
In-Reply-To: <Pine.LNX.4.63.0511111511050.7575@wbgn013.biozentrum.uni-wuerzburg.de>

  Hello,

Dear diary, on Fri, Nov 11, 2005 at 03:14:24PM CET, I got a letter
where Johannes Schindelin <Johannes.Schindelin@gmx.de> said that...
> On Fri, 11 Nov 2005, Simon Richter wrote:
> 
> > As someone who carries around git repositories on VFAT formatted USB 
> > sticks, I welcome our symlink-deprived overlords.
> 
> Please note that symlinks are much more performant than symrefs. Working a 
> lot with switching branches, this matters.

  this is interesting. What operations get slowed down noticeably in
particular? Do you have any timing testcases and data at hand?

  Thanks,

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.

  reply	other threads:[~2005-11-11 15:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-10 20:45 Getting rid of symlinks in .git? Petr Baudis
2005-11-11  9:15 ` Simon Richter
2005-11-11 12:43   ` Alex Riesen
2005-11-11 13:01     ` Petr Baudis
     [not found]     ` <437494B2.30309@hogyros.de>
2005-11-11 18:42       ` Alex Riesen
2005-11-15  2:22     ` Junio C Hamano
2005-11-15  7:13       ` Alex Riesen
2005-11-11 14:14   ` Johannes Schindelin
2005-11-11 15:05     ` Petr Baudis [this message]
2005-11-11 15:40       ` Johannes Schindelin
2005-11-11 15:49         ` Petr Baudis
2005-11-11 16:03           ` Johannes Schindelin
2005-11-11 15:55         ` Nick Hengeveld

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=20051111150530.GT30496@pasky.or.cz \
    --to=pasky@suse.cz \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=Simon.Richter@hogyros.de \
    --cc=git@vger.kernel.org \
    --cc=proski@gnu.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 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).