From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jeff King <peff@peff.net>,
Sverre Rabbelier <srabbelier@gmail.com>,
Pieter de Bie <pdebie@ai.rug.nl>,
git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2009, #07; Wed, 28)
Date: Sat, 31 Jan 2009 17:31:27 -0800 [thread overview]
Message-ID: <7vr62j0wpc.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: alpine.DEB.1.00.0901301415260.3586@pacific.mpi-cbg.de
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> How about installing
>
> [branch "master"]
> remote = origin
> merge = refs/heads/master
>
> by default? It is a safe bet that this will be the case for 99% of all
> users that want to clone an empty repository (especially if they are
> putting their public repositories on something like repo.or.cz, where you
> cannot change the default branch from "master" to something else).
I think this is a reasonable thing to do. Even though cloning from a void
is not entirely a reasonable thing to do to begin with, because we are
going ahead to allow it now, it would be the best thing to do when cloning
a repository served by the currently deployed git.
We _could_ do better if we were to resurrect my earlier series to add
"where does the HEAD point at" protocol extension, but even then we would
need a fallback like your suggestion when talking to older servers anyway.
next prev parent reply other threads:[~2009-02-01 1:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 2:06 What's cooking in git.git (Jan 2009, #07; Wed, 28) Junio C Hamano
2009-01-29 3:38 ` Jeff King
2009-01-29 3:51 ` Jeff King
2009-01-29 4:02 ` Jeff King
2009-01-29 4:22 ` Junio C Hamano
2009-01-29 11:27 ` Sverre Rabbelier
2009-01-29 11:37 ` Jeff King
2009-01-29 11:40 ` Pieter de Bie
2009-01-29 11:45 ` Sverre Rabbelier
2009-01-29 11:50 ` Jeff King
2009-01-29 12:20 ` Sverre Rabbelier
2009-01-30 4:51 ` Jeff King
2009-01-30 13:18 ` Johannes Schindelin
2009-01-30 16:26 ` Jeff King
2009-02-01 1:31 ` Junio C Hamano [this message]
2009-02-12 6:42 ` Junio C Hamano
2009-02-12 10:51 ` Sverre Rabbelier
2009-02-12 11:04 ` Johannes Schindelin
2009-02-12 21:04 ` Junio C Hamano
2009-02-12 21:51 ` Johannes Schindelin
2009-02-12 12:32 ` Jeff King
2009-01-29 11:48 ` Jeff King
2009-01-29 12:04 ` Nico -telmich- Schottelius
2009-01-30 4:59 ` Jeff King
2009-01-29 8:14 ` Charles Bailey
2009-01-29 8:26 ` Junio C Hamano
2009-01-29 9:16 ` Charles Bailey
2009-01-30 16:32 ` Charles Bailey
2009-02-01 17:45 ` Kirill Smelkov
2009-02-01 21:34 ` Junio C Hamano
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=7vr62j0wpc.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=pdebie@ai.rug.nl \
--cc=peff@peff.net \
--cc=srabbelier@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.