From: Denton Liu <liu.denton@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2019, #03; Tue, 19)
Date: Wed, 20 Nov 2019 15:32:14 -0800 [thread overview]
Message-ID: <20191120233214.GA17235@generichostname> (raw)
In-Reply-To: <xmqqftikxs4z.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Tue, Nov 19, 2019 at 04:05:48PM +0900, Junio C Hamano wrote:
[...]
> * dl/pretty-reference (2019-11-19) 11 commits
> - squash! pretty: implement 'reference' format
> - SubmittingPatches: use `--pretty=reference`
> - pretty: implement 'reference' format
> - pretty: provide short date format
> - t4205: cover `git log --reflog -z` blindspot
> - pretty.c: inline initalize format_context
> - revision: make get_revision_mark() return const pointer
> - completion: complete `tformat:` pretty format
> - SubmittingPatches: remove dq from commit reference
> - pretty-formats.txt: use generic terms for hash
> - SubmittingPatches: use generic terms for hash
>
> "git log" family learned "--pretty=ref" that gives the name of a
Since this will be used for release notes, could we use the full name of
the pretty format (i.e. "--pretty=reference")?
(Also, TIL that --pretty can match incomplete prefixes!)
> commit in the format that is often used to refer to it in log
> messages.
>
> Expecting finishing touches to the data handling.
> Other than that, this is reasonably well done, I think.
[...]
> * dl/t5520-cleanup (2019-11-19) 14 commits
> - t5520: replace `! git` with `test_must_fail git`
> - t5520: remove redundant lines in test cases
> - t5520: replace $(cat ...) comparison with test_cmp
> - t5520: don't put git in upstream of pipe
> - t5520: test single-line files by git with test_cmp
> - t5520: use test_cmp_rev where possible
> - t5520: replace test -{n,z} with test-lib functions
> - t5520: use test_line_count where possible
> - t5520: remove spaces after redirect operator
> - t5520: replace test -f with test-lib functions
> - t5520: let sed open its own input
> - t5520: use sq for test case names
> - t5520: improve test style
> - t: teach test_cmp_rev to accept ! for not-equals
>
> Test cleanup.
>
> Will merge to 'next'.
Any chance that we can queue this patch[1] either as a separate series
or as a precursor to the above?
Thanks,
Denton
[1]: https://public-inbox.org/git/20191114005215.GA24527@generichostname
next prev parent reply other threads:[~2019-11-20 23:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 7:05 What's cooking in git.git (Nov 2019, #03; Tue, 19) Junio C Hamano
2019-11-19 9:38 ` Danh Doan
2019-11-20 2:52 ` Junio C Hamano
2019-11-19 17:58 ` SZEDER Gábor
2019-11-20 3:02 ` Junio C Hamano
2019-11-20 13:58 ` Derrick Stolee
2019-11-21 0:36 ` Junio C Hamano
2019-11-21 11:10 ` Derrick Stolee
2019-11-22 5:42 ` Junio C Hamano
2019-11-19 18:01 ` ag/sequencer-todo-updates , was " Alban Gruin
2019-11-19 20:41 ` Jonathan Tan
2019-11-20 3:03 ` Junio C Hamano
2019-11-21 8:17 ` Alban Gruin
2019-11-23 0:47 ` Alban Gruin
2019-11-20 23:32 ` Denton Liu [this message]
2019-11-21 0:39 ` Junio C Hamano
2019-11-23 20:35 ` Philippe Blain
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=20191120233214.GA17235@generichostname \
--to=liu.denton@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).