From: Junio C Hamano <gitster@pobox.com>
To: Karthik Nayak <karthik.188@gmail.com>
Cc: git@vger.kernel.org, christian.couder@gmail.com,
Matthieu.Moy@grenoble-inp.fr
Subject: Re: [PATCH v5 01/11] t6301: for-each-ref tests for ref-filter APIs
Date: Wed, 24 Jun 2015 17:16:51 -0700 [thread overview]
Message-ID: <xmqqoak48wwc.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1435175632-27803-1-git-send-email-karthik.188@gmail.com> (Karthik Nayak's message of "Thu, 25 Jun 2015 01:23:42 +0530")
Karthik Nayak <karthik.188@gmail.com> writes:
> t/t6301-for-each-ref-filter.sh | 19 +++++++++++++++++++
t6301 is already used in mh/reporting-broken-refs-from-for-each-ref
topic. Please renumber.
next prev parent reply other threads:[~2015-06-25 0:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 19:51 [PATCH v5 00/11] add options to for-each-ref Karthik Nayak
2015-06-24 19:53 ` [PATCH v5 01/11] t6301: for-each-ref tests for ref-filter APIs Karthik Nayak
2015-06-24 19:53 ` [PATCH v5 02/11] tag: libify parse_opt_points_at() Karthik Nayak
2015-06-24 19:53 ` [PATCH v5 03/11] ref-filter: implement '--points-at' option Karthik Nayak
2015-06-24 19:53 ` [PATCH v5 04/11] for-each-ref: add " Karthik Nayak
2015-06-24 19:53 ` [PATCH v5 05/11] ref-filter: add parse_opt_merge_filter() Karthik Nayak
2015-06-24 19:53 ` [PATCH v5 06/11] ref-filter: implement '--merged' and '--no-merged' options Karthik Nayak
2015-06-24 19:53 ` [PATCH v5 07/11] for-each-ref: add " Karthik Nayak
2015-06-24 19:53 ` [PATCH v5 08/11] parse-option: rename parse_opt_with_commit() Karthik Nayak
2015-06-24 19:53 ` [PATCH v5 09/11] parse-options.h: add macros for '--contains' option Karthik Nayak
2015-06-24 19:53 ` [PATCH v5 10/11] ref-filter: implement " Karthik Nayak
2015-06-24 19:53 ` [PATCH v5 11/11] for-each-ref: add " Karthik Nayak
2015-06-25 0:16 ` Junio C Hamano [this message]
2015-06-25 8:40 ` [PATCH v5 01/11] t6301: for-each-ref tests for ref-filter APIs Karthik Nayak
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=xmqqoak48wwc.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.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.
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).