From: Jakub Narebski <jnareb@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: jidanni@jidanni.org, git@vger.kernel.org
Subject: Re: git-ls-files -l
Date: Tue, 30 Dec 2008 22:47:39 +0100 [thread overview]
Message-ID: <200812302247.40872.jnareb@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0812301226110.3082@localhost.localdomain>
On Tue, 30 Dec 2008, Linus Torvalds wrote:
> On Tue, 30 Dec 2008, Jakub Narebski wrote:
> >
> > I think it would be easy to add '-l' also to git-ls-files. Please
> > remember to provide size only for blobs, as provoding size for trees
> > would make it harder to change to future packv4, where tree objects
> > would be stored deconstructed.
>
> Personally, more than "git ls-files -l", I've occasionally wanted a real
> "git ls" that really looks more like "ls". That includes:
>
> - turning a list of files in a subdirectory into a "directory" entry
> (which is not very natural for "git ls-files" as an index operation,
> since the index is fundamentally flat).
>
> - yes, adding "-l" as an option, but really showing the stat information.
> Right now, you can do "git ls-files --stage", and it will show a kind
> of extended information, but while it shows the mode, it doesn't show
> the owner/timestamp/etc parts of the index, and those are sometimes
> interesting.
Good idea.
I guess we could put shortened sha-1 of object in place of owner and
group info which is not present in index, and perhaps stage number
instead of number of hard links. I wonder a bit about formatting
timestamps, if to follow "ls -l" format there...
> Btw, the "ls-tree -l" format is not nice. Don't use it as a basis
> to pattern "ls -l" (or if you want to just extend ls-tree, whatever).
Well, "ls-tree -l" is just "ls-tree" with size added. You would
probably want to use "git ls-tree -l --abbrev" instead for human
consumption.
--
Jakub Narebski
Poland
prev parent reply other threads:[~2008-12-30 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 17:07 git-ls-files -l jidanni
2008-12-30 11:01 ` Jakub Narebski
2008-12-30 20:32 ` Linus Torvalds
2008-12-30 21:47 ` Jakub Narebski [this message]
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=200812302247.40872.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=jidanni@jidanni.org \
--cc=torvalds@linux-foundation.org \
/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).