From: "Frans Klaver" <fransklaver@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>,
"Daniele Segato" <daniele.bilug@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>,
"Jeff King" <peff@peff.net>, "Scott Chacon" <schacon@gmail.com>
Subject: Re: Git ticket / issue tracking ERA: Git shouldn't allow to push a new branch called HEAD
Date: Wed, 23 Nov 2011 22:30:50 +0100 [thread overview]
Message-ID: <op.v5e4podr0aolir@keputer.lokaal> (raw)
In-Reply-To: <7v4nxudb73.fsf@alter.siamese.dyndns.org>
On Wed, 23 Nov 2011 18:02:08 +0100, Junio C Hamano <gitster@pobox.com>
wrote:
> Frans Klaver <fransklaver@gmail.com> writes:
>
>> The note from the maintainer[1] mentions
>>
>> git://git.kernel.org/pub/scm/git/git.git/
>> git://repo.or.cz/alt-git.git
>> https://github.com/git/git
>> https://code.google.com/p/git-core/
>>
>> I would assume one of those would be a nomination for 'official' repo.
>>
>> Maybe something for Scott C. to address?
>
> As long as the link says "Git source repository" without "the official",
> Scott is doing the right thing. It is just one of the copies that I push
> into, so it may be considered more official than a fork of my history by
> a
> random unknown person.
>
> As Git is distributed, we do not need a single "official" repository. If
> you really want to name one, my private working repository at my home
> machine would be what is closest to one, as patches and pull requests are
> processed there and then the result is pushed out to the above four and a
> few others. But that "official" one is not exposed to the outside world
> ;-)
Since official is a rather unreal term here, let's just drop it. There are
a few repositories that the maintainer currently pushes to, and those are
the most reliable ones to use if you want the latest git vanilla. Other
than that, there's going to be no difference from the next git.git clone.
It might remove some confusion if these repos would be reflected on
websites focusing on git as they are in the maintainers notes, but that's
probably up to the respective webmasters then.
Frans
prev parent reply other threads:[~2011-11-23 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 14:04 Git ticket / issue tracking ERA: Git shouldn't allow to push a new branch called HEAD Daniele Segato
[not found] ` <CAH5451==iXuB=QPW7bQvahB-jMnKC2axJYnW2OfFq=UNO9U6mg@mail.gmail.com>
2011-11-22 15:56 ` Daniele Segato
2011-11-22 19:46 ` Junio C Hamano
2011-11-22 19:41 ` Junio C Hamano
2011-11-23 13:44 ` Paolo Ciarrocchi
2011-11-23 15:47 ` Frans Klaver
2011-11-23 17:02 ` Junio C Hamano
2011-11-23 21:30 ` Frans Klaver [this message]
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=op.v5e4podr0aolir@keputer.lokaal \
--to=fransklaver@gmail.com \
--cc=daniele.bilug@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=paolo.ciarrocchi@gmail.com \
--cc=peff@peff.net \
--cc=schacon@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 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).