From: Ralf Thielow <ralf.thielow@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2012, #02; Fri, 9)
Date: Fri, 9 Nov 2012 21:06:47 +0100 [thread overview]
Message-ID: <CAN0XMOL1SS2iiJkZyt3HACoCRXE1nGrd52B2rscWyS1e7X0GWQ@mail.gmail.com> (raw)
In-Reply-To: <CAN0XMO+sgSgkqK7D6=5NL--rMYBwsGohgQ7v+ja4Twub20N1sQ@mail.gmail.com>
On Fri, Nov 9, 2012 at 9:01 PM, Ralf Thielow <ralf.thielow@gmail.com> wrote:
> On Fri, Nov 9, 2012 at 8:23 PM, Jeff King <peff@peff.net> wrote:
>>
>> You can find the changes described here in the integration branches of
>> my repository at:
>>
>> git://github.com/peff/git.git
>
> It seems that the repo doesn't contain the integration branches?!?
>
> $ git remote add peff git://github.com/peff/git.git
> $ git fetch -v peff
> From git://github.com/peff/git
> * [new branch] maint -> peff/maint
> * [new branch] master -> peff/master
> * [new branch] next -> peff/next
> * [new branch] pu -> peff/pu
> * [new branch] todo -> peff/todo
> $
But "integration branches" means "master", "next" and "pu" than I haven't
said anything. ;) Sorry for the noise.
next prev parent reply other threads:[~2012-11-09 20:07 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 19:23 What's cooking in git.git (Nov 2012, #02; Fri, 9) Jeff King
2012-11-09 20:01 ` Ralf Thielow
2012-11-09 20:06 ` Ralf Thielow [this message]
2012-11-09 20:10 ` Jeff King
2012-11-09 20:27 ` Junio C Hamano
2012-11-10 0:38 ` Jeff King
2012-11-10 17:14 ` Junio C Hamano
2012-11-09 21:52 ` Kalle Olavi Niemitalo
2012-11-10 15:52 ` Paul Fox
2012-11-10 19:32 ` Kalle Olavi Niemitalo
2012-11-10 21:12 ` Andreas Schwab
2012-11-10 22:08 ` Paul Fox
2012-11-11 7:02 ` Kalle Olavi Niemitalo
2012-11-11 8:58 ` Andreas Schwab
2012-11-11 15:48 ` Jeff King
2012-11-11 16:31 ` [PATCH 0/5] ignore SIGINT while editor runs Jeff King
2012-11-11 16:55 ` [PATCH 1/5] launch_editor: refactor to use start/finish_command Jeff King
2012-11-11 16:55 ` [PATCH 2/5] launch_editor: ignore SIGINT while the editor has control Paul Fox
2012-11-12 17:44 ` Junio C Hamano
2012-11-12 19:47 ` Jeff King
2012-11-11 16:55 ` [PATCH 3/5] run-command: drop silent_exec_failure arg from wait_or_whine Jeff King
2012-11-11 18:13 ` Felipe Contreras
2012-11-11 16:56 ` [PATCH 4/5] run-command: do not warn about child death by SIGINT Jeff King
2012-11-11 16:57 ` [PATCH 5/5] launch_editor: propagate SIGINT from editor to git Jeff King
2012-11-11 19:48 ` Johannes Sixt
2012-11-30 20:24 ` Jeff King
2012-11-11 16:58 ` [PATCH 2/5] launch_editor: ignore SIGINT while the editor has control Jeff King
2012-11-11 18:27 ` [PATCH 0/5] ignore SIGINT while editor runs Paul Fox
2012-11-11 19:15 ` Krzysztof Mazur
2012-11-11 20:24 ` Paul Fox
2012-11-11 20:43 ` Krzysztof Mazur
2012-11-11 22:08 ` Andreas Schwab
2012-11-09 23:21 ` What's cooking in git.git (Nov 2012, #02; Fri, 9) Felipe Contreras
2012-11-10 0:33 ` Jeff King
2012-11-10 0:44 ` Felipe Contreras
2012-11-10 12:32 ` SZEDER Gábor
2012-11-10 19:13 ` Felipe Contreras
2012-11-10 19:56 ` 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=CAN0XMOL1SS2iiJkZyt3HACoCRXE1nGrd52B2rscWyS1e7X0GWQ@mail.gmail.com \
--to=ralf.thielow@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).