From: Scott Chacon <schacon@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2011, #06; Wed, 21)
Date: Fri, 23 Sep 2011 07:44:13 -0700 [thread overview]
Message-ID: <CAP2yMaL3rewYZSXQFxkSLkiNbaBAP8r707x2dScVK1zeVr8hXQ@mail.gmail.com> (raw)
In-Reply-To: <7vaa9xyxpf.fsf@alter.siamese.dyndns.org>
Hey,
On Wed, Sep 21, 2011 at 10:04 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Here are the topics that have been cooking. Commits prefixed with '-' are
> only in 'pu' while commits prefixed with '+' are in 'next'.
>
> Here are the repositories that have my integration branches:
>
> With maint, master, next, pu and todo:
>
> url = git://repo.or.cz/alt-git.git
> url = https://code.google.com/p/git-core/
>
> With only maint and master:
>
> url = git://git.sourceforge.jp/gitroot/git-core/git.git
> url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core
>
> With all the topics and integration branches:
>
> url = https://github.com/gitster/git
>
It appears that you're no longer pushing the 'html' branch to the
GitHub repo, but you are to some of the other ones, which is sort of
strange because *everything* else is there.
Since the k.org hosting of the man pages is down, I was working on
putting them on git-scm.com, where you could select which version of
the docs you want to see and could search through them and whatnot.
Can you push 'html' to GitHub too? I want to pull my data out of it
on an ongoing basis and it's the only one with a git object level API.
Thanks,
Scott
next prev parent reply other threads:[~2011-09-23 14:44 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 ` Scott Chacon [this message]
2011-09-23 18:00 ` What's cooking in git.git (Sep 2011, #06; Wed, 21) 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
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=CAP2yMaL3rewYZSXQFxkSLkiNbaBAP8r707x2dScVK1zeVr8hXQ@mail.gmail.com \
--to=schacon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).