From: Pavel Roskin <proski@gnu.org>
To: Petr Baudis <pasky@suse.cz>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: [PATCH] Disable USE_SYMLINK_HEAD by default
Date: Tue, 15 Nov 2005 12:06:15 -0500 [thread overview]
Message-ID: <1132074375.25640.47.camel@dv> (raw)
In-Reply-To: <20051115121854.GV30496@pasky.or.cz>
On Tue, 2005-11-15 at 13:18 +0100, Petr Baudis wrote:
> Dear diary, on Tue, Nov 15, 2005 at 12:09:42PM CET, I got a letter
> where Johannes Schindelin <Johannes.Schindelin@gmx.de> said that...
> > I think Junio is right: we should not force everybody not to use symlinks,
> > only because there happens to be VFAT-, SMB- or HTTP-shared repositories.
> > As Junio says, if there are people experiencing problems because they lack
> > symbolic links, they should fix it.
>
> I'm ambivalent here. I would like to have just a single behaviour here,
> since the symbolic ref otherwise really does not get much testing. But I
> can also understand that we are breaking tools here.
>
> Still, for the reason above, I think we should aim at the symbolic refs
> being the canonical format in the next major release after 1.0, giving
> users time to fix their tools. I can see no advantage in symlinks except
> the backwards compatibility - speed argument was presented, but I don't
> buy that until I see hard data supporting that.
I planned to write about symrefs long ago, and probably I waited for too
long. I still hope it will be the default for 1.0 release, but if not,
I hope the next release won't be too far away.
> > On the other hand, I think it would be useful to be able to configure the
> > behaviour via .git/config.
>
> Yes, I would very much like to have this. I still want to go
> symrefs-only for public repositories created for cg-admin-setuprepo, so
> that fetching over HTTP works properly.
Agreed. By the way, the symref doesn't need to be called HEAD - it
could be "trunk" or "main" or "default-branch".
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2005-11-15 17:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 5:59 [PATCH] Disable USE_SYMLINK_HEAD by default Pavel Roskin
2005-11-15 7:03 ` Junio C Hamano
2005-11-15 8:13 ` Pavel Roskin
2005-11-15 8:24 ` Junio C Hamano
2005-11-15 10:24 ` Junio C Hamano
2005-11-15 11:09 ` Johannes Schindelin
2005-11-15 12:18 ` Petr Baudis
2005-11-15 14:24 ` Johannes Schindelin
2005-11-15 15:37 ` Adrien Beau
2005-11-15 16:50 ` Pavel Roskin
2005-11-15 17:05 ` Junio C Hamano
2005-11-15 17:21 ` Pavel Roskin
2005-11-15 17:32 ` Nick Hengeveld
2005-11-15 17:33 ` Linus Torvalds
2005-11-15 17:42 ` Petr Baudis
2005-11-15 18:01 ` Linus Torvalds
2005-11-15 18:13 ` Junio C Hamano
2005-11-15 17:06 ` Pavel Roskin [this message]
2005-11-15 18:21 ` Junio C Hamano
2005-11-16 1:56 ` Pavel Roskin
2005-11-16 3:13 ` Junio C Hamano
2005-11-16 1:05 ` Josef Weidendorfer
2005-11-15 10:31 ` Catalin Marinas
2005-11-15 16:27 ` Pavel Roskin
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=1132074375.25640.47.camel@dv \
--to=proski@gnu.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=pasky@suse.cz \
/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).