From: Joshua Nelson <jyn514@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] ls-tree: make <tree-ish> optional
Date: Tue, 3 Jul 2018 20:05:20 -0400 [thread overview]
Message-ID: <368608dc-4351-541c-0236-9f5760ca5d97@gmail.com> (raw)
In-Reply-To: <20180703235337.31770-1-jyn514@gmail.com>
On 07/03/2018 07:53 PM, Joshua Nelson wrote:
> diff --git a/t/t3104-ls-tree-optional-args.sh b/t/t3104-ls-tree-optional-args.sh
> new file mode 100755
> index 000000000..e9d8389bc
> --- /dev/null
> +++ b/t/t3104-ls-tree-optional-args.sh
> @@ -0,0 +1,63 @@
> +#!/bin/sh
> +
> +test_description='ls-tree test (optional args)
> +
> +This test runs git-ls-tree with ambiguous positional options.'
> +
> +# cat appends newlines after every file
> +test_expect_success 'show HEAD when given no args' '
> + if [ "$(git ls-tree)" != "$(cat expected1 expected2)" ]; then false; fi
> +'
I forgot to take out the comment about cat; it's not actually true, I
just happened to be using echo instead of printf when I wrote it.
Is it customary to send a new patch or second patch that builds on the
first? If I specify a commit range to git-send-email it sends both, not
just the latest.
next prev parent reply other threads:[~2018-07-04 0:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 3:58 [PATCH 1/3] ls-tree: make <tree-ish> optional Joshua Nelson
2018-07-03 3:58 ` [PATCH 2/3] ls-tree: update usage info Joshua Nelson
2018-07-03 7:14 ` Elijah Newren
2018-07-03 7:18 ` Eric Sunshine
2018-07-03 3:58 ` [PATCH 3/3] ls-tree: add unit tests for arguments Joshua Nelson
2018-07-03 7:30 ` Elijah Newren
2018-07-03 7:33 ` Eric Sunshine
2018-07-03 7:12 ` [PATCH 1/3] ls-tree: make <tree-ish> optional Elijah Newren
2018-07-03 22:05 ` Junio C Hamano
2018-07-03 22:55 ` Elijah Newren
2018-07-03 22:58 ` Joshua Nelson
2018-07-06 17:01 ` Junio C Hamano
2018-07-06 21:26 ` Joshua Nelson
2018-07-06 21:32 ` Junio C Hamano
2018-07-03 7:15 ` Eric Sunshine
2018-07-03 23:15 ` Joshua Nelson
2018-07-03 23:53 ` [PATCH] " Joshua Nelson
2018-07-04 0:05 ` Joshua Nelson [this message]
2018-07-04 9:38 ` Eric Sunshine
2018-07-04 10:04 ` Eric Sunshine
2018-07-04 9:29 ` [PATCH 1/3] " Eric Sunshine
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=368608dc-4351-541c-0236-9f5760ca5d97@gmail.com \
--to=jyn514@gmail.com \
--cc=git@vger.kernel.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.
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).