git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Andrey <ahippo@yandex.ru>
To: Junio C Hamano <gitster@pobox.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Cc: luke@diamand.org
Subject: Re: What's cooking in git.git (Jun 2019, #05; Wed, 19)
Date: Sat, 22 Jun 2019 05:46:50 -0400	[thread overview]
Message-ID: <1748011561196810@sas2-7b909973f402.qloud-c.yandex.net> (raw)
In-Reply-To: <xmqqef3oq3go.fsf@gitster-ct.c.googlers.com>

20.06.2019, 00:35, "Junio C Hamano" <gitster@pobox.com>:
> * am/p4-branches-excludes (2019-04-02) 8 commits
>  - git-p4: respect excluded paths when detecting branches
>  - git-p4: add failing test for "git-p4: respect excluded paths when detecting branches"
>  - git-p4: don't exclude other files with same prefix
>  - git-p4: add failing test for "don't exclude other files with same prefix"
>  - git-p4: don't groom exclude path list on every commit
>  - git-p4: match branches case insensitively if configured
>  - git-p4: add failing test for "git-p4: match branches case insensitively if configured"
>  - git-p4: detect/prevent infinite loop in gitCommitByP4Change()
>
>  "git p4" update.
>
>  Is this ready for 'next'?

Junio,

I haven't got any new feedback on the patch series in the past 2.5 months.
From my point of view, these are ready for next.

Thank you,
Andrey.


  parent reply	other threads:[~2019-06-22  9:54 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 [this message]
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
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=1748011561196810@sas2-7b909973f402.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).