All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: demerphq <demerphq@gmail.com>
Cc: John Tapsell <johnflux@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: Relative ls-files
Date: Wed, 23 Mar 2011 12:42:54 +0100	[thread overview]
Message-ID: <4D89DCBE.3060400@drmicha.warpmail.net> (raw)
In-Reply-To: <AANLkTimdLGgGXGRNVH5+X-cnhK2NWfWx9k0apt-6rr1Z@mail.gmail.com>

demerphq venit, vidit, dixit 23.03.2011 12:28:
> On 23 March 2011 12:27, John Tapsell <johnflux@gmail.com> wrote:
>> On 23 March 2011 10:49, Michael J Gruber <git@drmicha.warpmail.net> wrote:
>>> John Tapsell venit, vidit, dixit 23.03.2011 11:33:
>>>> Hi,
>>>>
>>>>   Could someone add a feature to  ls-files  to list all the files in
>>>> the repository, but relative to the current path?  It would be useful
>>>> for many different aliases, such as "git locate".
>>>
>>> That is in the works, we just have to decide between two suggested
>>> notations:
>>>
>>> git ls-files :
>>> git ls-files :/
>>
>>
>> What's wrong with --relative  or something?

??

ls-files already lists files relative to cwd. What you need is a way to
specify that you want all files, not just those beneath cwd.

>>
>> I've never liked magical strange notations.  ":" already has a meaning.
> 
> +1

I think you've both been missing out on the discussions about
--full-tree and refspec notation for that...

Of course ":" has a meaning. "git show HEAD:" lists all files at the
top-level of the tree at HEAD. That is exactly why ":" has been
suggested to denote the top-level for pathspecs also. Note that this is
much more general than just an option for ls-files.

Michael

  reply	other threads:[~2011-03-23 11:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23 10:33 Relative ls-files John Tapsell
2011-03-23 10:49 ` Michael J Gruber
2011-03-23 11:27   ` John Tapsell
2011-03-23 11:28     ` demerphq
2011-03-23 11:42       ` Michael J Gruber [this message]
2011-03-23 13:54         ` Martin Langhoff
2011-03-23 14:09           ` Junio C Hamano
2011-03-23 14:14             ` Nguyen Thai Ngoc Duy
2011-03-23 15:20               ` Junio C Hamano
2011-03-23 15:41                 ` Nguyen Thai Ngoc Duy
2011-03-23 22:44                   ` Junio C Hamano
2011-03-24 13:26                     ` Nguyen Thai Ngoc Duy
2011-03-24 14:41                       ` [PATCH 1/2] Reimplement read_tree_recursive() using tree_entry_interesting() Nguyễn Thái Ngọc Duy
2011-03-24 14:41                         ` [PATCH 2/2] Convert read_tree{,_recursive} to support struct pathspec Nguyễn Thái Ngọc Duy
2011-03-24 14:49                           ` Nguyen Thai Ngoc Duy
2011-03-24 19:58                           ` Junio C Hamano
2011-03-24 19:07                         ` [PATCH 1/2] Reimplement read_tree_recursive() using tree_entry_interesting() Junio C Hamano
2011-03-24 19:55                         ` Junio C Hamano
2011-03-25  9:34                           ` [PATCH 1/3] " Nguyễn Thái Ngọc Duy
2011-03-25  9:34                             ` [PATCH 2/3] Convert read_tree{,_recursive} to support struct pathspec Nguyễn Thái Ngọc Duy
2011-03-25  9:34                             ` [PATCH 3/3] Improve tree_entry_interesting() handling code Nguyễn Thái Ngọc Duy
2011-03-24 14:47                       ` Relative ls-files Junio C Hamano
2011-03-23 14:46             ` Martin Langhoff
2011-03-23 15:24               ` Junio C Hamano
2011-03-23 17:35             ` Junio C Hamano
2011-03-23 15:42         ` Junio C Hamano
2011-03-23 15:57           ` Michael J Gruber
2011-03-23 16:10             ` 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=4D89DCBE.3060400@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=demerphq@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=johnflux@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.