git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Petr Baudis <pasky@suse.cz>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	git@vger.kernel.org
Subject: Re: [PATCH] Disable USE_SYMLINK_HEAD by default
Date: Tue, 15 Nov 2005 12:21:35 -0500	[thread overview]
Message-ID: <1132075295.25640.59.camel@dv> (raw)
In-Reply-To: <7v8xvpn8ne.fsf@assigned-by-dhcp.cox.net>

On Tue, 2005-11-15 at 09:05 -0800, Junio C Hamano wrote:
> Petr Baudis <pasky@suse.cz> writes:
> 
> > 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.
> 
> Sorry, I must have missed that part.  How does fetch-over-HTTP
> break with symlinked HEAD?

With symlinks, cogito doesn't know which branch it is fetching if the
branch is not explicitly specified.

The old behavior was to fetch the "master" branch by default.
Currently, cogito uses HEAD, but it cannot read the symlink, it can only
read the SHA1.  So, if somebody decides to use "cg-switch" on the public
repository (admittedly not a very good idea), all the clients that are
not using an explicit branch will unknowingly switch to another branch
upon update.

It also could be useful for users to know the branch name.  I, for one,
would like to know if HEAD links to "stable" or "sandbox4crazyhacks",
even if both have the same SHA1 at the moment.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2005-11-15 17:22 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 [this message]
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
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=1132075295.25640.59.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).