From: Junio C Hamano <gitster@pobox•com>
To: git@vger•kernel.org
Cc: Scott Chacon <schacon@gmail•com>
Subject: Re: What's cooking in git.git (Sep 2011, #06; Wed, 21)
Date: Mon, 26 Sep 2011 11:52:53 -0700 [thread overview]
Message-ID: <7vmxdr2l16.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAP2yMaL=Ox7mFQSA8yyOB9CoBaa_pQQ3bE4B9FugOnfJCT6XeA@mail.gmail.com> (Scott Chacon's message of "Mon, 26 Sep 2011 07:03:03 -0700")
Scott Chacon <schacon@gmail•com> writes:
> On Fri, Sep 23, 2011 at 12:29 PM, Junio C Hamano <gitster@pobox•com> wrote:
>> It just occurred to me that https://github.com/git/git repository might be
>> the one you are talking about, but that repository is not even mine. The
>> page at https://github.com/git says git@logicalawesome•com is its contact
>> person.
>>
>> I _suspect_ it is set up to mirror from my k.org repository and obviously
>> nothing is updated from that route for the past few weeks. It is correct
>> to say "html branch in that repository is no longer updated", but I cannot
>> do anything about that repository ;-).
>
> git/git is a mirror I set up from k.org years ago for git-scm.com. I
> believe you've been a collaborator on it for a while now, so you can
> push to it if you'd like. The mirroring system is down since k.org
> died and I've since moved it off the host I had been using to Heroku,
> so I can't do the mirroring that way anymore. If you want to push to
> it I'll leave it there, otherwise I'll reroot your repo to be the head
> of the GitHub network instead.
Ok, to clarify this discussion for people who have been pulling from me
and have been wondering where to reset their "origin" to...
* I'll start to also push into https://github.com/git/git/ directly,
treating it like git://repo.or.cz/alt-git.git/ and other secondary
distribution points, that have the integration branches, todo, html and
man.
* Eventually git://git.kernel.org/pub/scm/git/git.git/ will again start
receiving my direct pushes just like it used to. The secondary
distribution points will also get my pushes directly (I've made sure
with Scott that mirroring into https://github.com/git/git/ from my
k.org repository will stay turned off).
* https://github.com/gitster/git.git/ will stay a mirror of my private
development repository with the topic branches (but without non-source
branches like html and mah).
I haven't figured out how the preformatted documentation branches will be
managed in the longer term, as it seems likely that I no longer would have
the post-update hook access to update them upon pushing into my k.org
repository. I might end up dropping these branches altogether if it gets
too cumbersome for me to maintain, but I do not know yet.
next prev parent reply other threads:[~2011-09-26 18:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 5:04 What's cooking in git.git (Sep 2011, #06; Wed, 21) Junio C Hamano
2011-09-22 8:37 ` Carlos Martín Nieto
2011-09-22 9:14 ` Michael Schubert
2011-09-22 16:39 ` Junio C Hamano
2011-09-22 23:01 ` Jakub Narebski
2011-09-22 23:12 ` Junio C Hamano
2011-09-22 23:33 ` Jakub Narebski
2011-09-22 23:45 ` Junio C Hamano
2011-09-23 11:00 ` [PATCH] fix push --quiet: add 'quiet' capability to receive-pack Clemens Buchacher
2011-09-23 11:55 ` [PATCH] use -h for synopsis and --help for manpage consistently Clemens Buchacher
2011-09-23 14:44 ` What's cooking in git.git (Sep 2011, #06; Wed, 21) Scott Chacon
2011-09-23 18:00 ` Junio C Hamano
2011-09-23 19:29 ` Junio C Hamano
2011-09-26 14:03 ` Scott Chacon
2011-09-26 18:52 ` Junio C Hamano [this message]
2011-09-27 2:08 ` Jay Soffian
[not found] ` <20111003182136.GA6136@ecki.lan>
2011-10-03 22:03 ` [PATCH] use -h for synopsis and --help for manpage consistently Junio C Hamano
2011-10-05 6:33 ` Clemens Buchacher
2011-10-05 6:31 ` [PATCH] fix push --quiet: add 'quiet' capability to receive-pack Clemens Buchacher
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=7vmxdr2l16.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=schacon@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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