All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kan-Ru Chen <kanru@kanru.info>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/3] Bringing git-ls-files to porcelain level
Date: Mon, 01 Nov 2010 18:30:57 +0800	[thread overview]
Message-ID: <87zkttqqse.fsf@anar.kanru.info> (raw)
In-Reply-To: <1262884076-12293-1-git-send-email-pclouds@gmail.com> (=?utf-8?B?Ik5ndXnhu4VuCVRow6FpIE5n4buNYw==?= Duy"'s message of "Fri, 8 Jan 2010 00:07:53 +0700")

Hi,

Nguyễn Thái Ngọc Duy <pclouds@gmail.com> writes:

> This is a hack, to scratch my itch. These patches add "git ls",
> which is equivalent to "git ls-files --max-depth 1|column"

What is the status of this patch?

I found it might be useful for zsh completion codes. Currently zsh _git
completion relies heavily on ls-files and can be very slow on large
repository like linux kernel.

If ls-files supports --max-depth then zsh can do incremental
completion. (hopefully)

  kanru

-- 
“A badly written book is only a blunder. A bad
 translation of a good book is a crime.” -- Gilbert Highet

  parent reply	other threads:[~2010-11-01 11:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07 17:07 [PATCH 0/3] Bringing git-ls-files to porcelain level Nguyễn Thái Ngọc Duy
2010-01-07 17:07 ` [PATCH 1/3] ls-files: support --max-depth Nguyễn Thái Ngọc Duy
2010-01-07 17:07 ` [PATCH 2/3] ls-files: support -o --max-depth (more of a hack as fill_directory should support this) Nguyễn Thái Ngọc Duy
2010-01-07 18:01   ` Junio C Hamano
2010-01-07 17:07 ` [PATCH 3/3] Add "ls", which is basically ls-files with user-friendly settings Nguyễn Thái Ngọc Duy
2010-01-07 18:01   ` Junio C Hamano
2010-01-07 18:09     ` Nguyen Thai Ngoc Duy
2010-01-08 14:16       ` Nguyen Thai Ngoc Duy
2010-01-07 18:12   ` Matthieu Moy
2010-01-07 17:40 ` [PATCH 0/3] Bringing git-ls-files to porcelain level Matthieu Moy
2010-01-07 17:47   ` Nguyen Thai Ngoc Duy
2010-11-01 10:30 ` Kan-Ru Chen [this message]
2010-11-01 11:20   ` Nguyen Thai Ngoc Duy

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=87zkttqqse.fsf@anar.kanru.info \
    --to=kanru@kanru.info \
    --cc=git@vger.kernel.org \
    --cc=pclouds@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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.