From: Duy Nguyen <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Apr 2015, #04; Mon, 27)
Date: Thu, 30 Apr 2015 08:07:00 +0700 [thread overview]
Message-ID: <CACsJy8BYhwcewEdix1WaAY+ukeTfwkLyrcimJ2K7Rgwh0E6EDQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqr3r5uyqg.fsf@gitster.dls.corp.google.com>
On Tue, Apr 28, 2015 at 3:01 AM, Junio C Hamano <gitster@pobox.com> wrote:
> * nd/list-files (2015-02-09) 21 commits
> - t3080: tests for git-list-files
> - list-files: -M aka diff-cached
> - list-files -F: show submodules with the new indicator '&'
> - list-files: add -F/--classify
> - list-files: show directories as well as files
> - list-files: do not show duplicate cached entries
> - list-files: sort output and remove duplicates
> - list-files: add -t back
> - list-files: add -1 short for --no-column
> - list-files: add -R/--recursive short for --max-depth=-1
> - list-files: -u does not imply showing stages
> - list-files: make alias 'ls' default to 'list-files'
> - list-files: a user friendly version of ls-files and more
> - ls-files: support --max-depth
> - ls-files: add --column
> - ls-files: add --color to highlight file names
> - ls-files: buffer full item in strbuf before printing
> - ls_colors.c: highlight submodules like directories
> - ls_colors.c: add a function to color a file name
> - ls_colors.c: parse color.ls.* from config file
> - ls_colors.c: add $LS_COLORS parsing code
>
> A new "git list-files" Porcelain command, "ls-files" with bells and
> whistles.
>
> Reroll to base on wt-status work ($gmane/265142) has seen some
> positive discussions.
>
> Waiting for a further polished reroll ($gmane/265534).
I'm a little bit busy with other things, so please drop this for now.
I'll resubmit when I address all the comments from the last round.
--
Duy
next prev parent reply other threads:[~2015-04-30 1:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 20:01 What's cooking in git.git (Apr 2015, #04; Mon, 27) Junio C Hamano
2015-04-29 22:42 ` Junio C Hamano
2015-04-29 22:50 ` Koosha Khajehmoogahi
2015-04-30 1:38 ` Junio C Hamano
2015-04-30 0:18 ` Paul Tan
2015-04-30 1:37 ` Junio C Hamano
2015-04-30 1:02 ` Jeff King
2015-04-30 1:36 ` Junio C Hamano
2015-04-30 6:55 ` Michael Haggerty
2015-04-30 8:00 ` Michael J Gruber
2015-04-30 8:21 ` Michael Haggerty
2015-04-30 1:07 ` Duy Nguyen [this message]
2015-04-30 1:35 ` Junio C Hamano
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=CACsJy8BYhwcewEdix1WaAY+ukeTfwkLyrcimJ2K7Rgwh0E6EDQ@mail.gmail.com \
--to=pclouds@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.
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).