From: Martin Langhoff <martin.langhoff@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: demerphq <demerphq@gmail.com>, John Tapsell <johnflux@gmail.com>,
Git List <git@vger.kernel.org>
Subject: Re: Relative ls-files
Date: Wed, 23 Mar 2011 09:54:45 -0400 [thread overview]
Message-ID: <AANLkTi=BrgZe47Bt5evr_qFzKBL=MY-6NmH22gsRurVV@mail.gmail.com> (raw)
In-Reply-To: <4D89DCBE.3060400@drmicha.warpmail.net>
On Wed, Mar 23, 2011 at 7:42 AM, Michael J Gruber
<git@drmicha.warpmail.net> wrote:
> Of course ":" has a meaning. "git show HEAD:" lists all files at the
> top-level of the tree at HEAD.
I got excited for a moment... now tested it and there isn't a recursive flag :-(
I've been pining for something easy and intuitive like git ls-files
<treeish>. You can do git ls-files --with-tree=<treeish> but I find it
very counter-intuitive.
Context: in some projects, I need to ask
- is this file in branch foo?
- has this file moved in branch foo?
- what files with extension .zoo exist in branch foo?
and the answer is git ls-files --with-tree=<treeish> | grep <regex> .
But the --with-tree param is so counterintuitive to me that I read the
manpage, everytime.
Not sure whether the bug is in me or in git, but it sure hits some
cognitive dissonance.
m
--
martin.langhoff@gmail.com
martin@laptop.org -- Software Architect - OLPC
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
next prev parent reply other threads:[~2011-03-23 13:55 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
2011-03-23 13:54 ` Martin Langhoff [this message]
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='AANLkTi=BrgZe47Bt5evr_qFzKBL=MY-6NmH22gsRurVV@mail.gmail.com' \
--to=martin.langhoff@gmail.com \
--cc=demerphq@gmail.com \
--cc=git@drmicha.warpmail.net \
--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 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).