From: Andrey <ahippo@yandex.ru>
To: Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
"luke@diamand.org" <luke@diamand.org>
Subject: Re: What's cooking in git.git (Jun 2019, #05; Wed, 19)
Date: Thu, 11 Jul 2019 22:20:22 -0400 [thread overview]
Message-ID: <17402391562898022@iva6-161d47f95e63.qloud-c.yandex.net> (raw)
In-Reply-To: <xmqqr27hftl2.fsf@gitster-ct.c.googlers.com>
25.06.2019, 13:44, "Junio C Hamano" <gitster@pobox.com>:
> Andrey <ahippo@yandex.ru> writes:
>
>>> Thanks. When I ask "Is this ready", I am asking for opinion(s) from
>>> third-party, not self nomination ;-)
>>
>> Ah, ok, sorry. :)
>> I just haven't seen any related comments to any of your previous "What's cooking" emails,
>> so thought I should send a keepalive email just in case.
>>
>>> Let's merge it down to 'next' and to 'master' anyway.
>> Thank you! That'll be great!
>
> Thank *you* (and also Luke) for keeping "git p4" alive ;)
It's mostly Luke and others.
git p4 made my life with Perforce tolerable.
Without git-p4 it would have been much worse.
--
Andrey.
next prev parent reply other threads:[~2019-07-12 2:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 4:35 What's cooking in git.git (Jun 2019, #05; Wed, 19) Junio C Hamano
2019-06-21 19:29 ` sg/rebase-progress, was " Johannes Schindelin
2019-06-21 20:42 ` Junio C Hamano
2019-06-21 20:06 ` md/list-objects-filter-combo, " Johannes Schindelin
2019-06-22 9:46 ` Andrey
2019-06-24 17:05 ` Junio C Hamano
2019-06-25 9:45 ` Andrey
2019-06-25 17:44 ` Junio C Hamano
2019-07-12 2:20 ` Andrey [this message]
2019-07-12 6:11 ` Luke Diamand
2019-06-26 9:02 ` Phillip Wood
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17402391562898022@iva6-161d47f95e63.qloud-c.yandex.net \
--to=ahippo@yandex.ru \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=luke@diamand.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).