From: Brandon Williams <bmwill@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2016, #08; Tue, 27)
Date: Wed, 28 Dec 2016 10:18:08 -0800 [thread overview]
Message-ID: <20161228181808.GC33595@google.com> (raw)
In-Reply-To: <xmqqy3z155o1.fsf@gitster.mtv.corp.google.com>
On 12/27, Junio C Hamano wrote:
> * bw/pathspec-cleanup (2016-12-14) 16 commits
> - pathspec: rename prefix_pathspec to init_pathspec_item
> - pathspec: small readability changes
> - pathspec: create strip submodule slash helpers
> - pathspec: create parse_element_magic helper
> - pathspec: create parse_long_magic function
> - pathspec: create parse_short_magic function
> - pathspec: factor global magic into its own function
> - pathspec: simpler logic to prefix original pathspec elements
> - pathspec: always show mnemonic and name in unsupported_magic
> - pathspec: remove unused variable from unsupported_magic
> - pathspec: copy and free owned memory
> - pathspec: remove the deprecated get_pathspec function
> - ls-tree: convert show_recursive to use the pathspec struct interface
> - dir: convert fill_directory to use the pathspec struct interface
> - dir: remove struct path_simplify
> - mv: remove use of deprecated 'get_pathspec()'
>
> Code clean-up in the pathspec API.
>
> Waiting for the (hopefully) final round of review before 'next'.
What more needs to be reviewed for this series?
--
Brandon Williams
next prev parent reply other threads:[~2016-12-28 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-27 23:11 What's cooking in git.git (Dec 2016, #08; Tue, 27) Junio C Hamano
2016-12-28 18:18 ` Brandon Williams [this message]
2016-12-29 10:06 ` Duy Nguyen
2017-01-03 12:20 ` Duy Nguyen
2017-01-03 17:58 ` Brandon Williams
2016-12-29 10:10 ` Lars Schneider
2017-01-03 18:54 ` Brandon Williams
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=20161228181808.GC33595@google.com \
--to=bmwill@google.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.
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).