From: Jonathan Nieder <jrnieder@gmail.com>
To: Eli Barzilay <eli@barzilay.org>
Cc: git@vger.kernel.org
Subject: Re: git check-attr in bare repositories
Date: Tue, 30 Mar 2010 16:22:22 -0500 [thread overview]
Message-ID: <20100330212222.GA11192@progeny.tock> (raw)
In-Reply-To: <19377.33747.838003.360864@winooski.ccs.neu.edu>
Eli Barzilay wrote:
> Well, using the index this way seems like a kind of a hack anyway, so
> I'm not sure that there is any reason to do this.
Most git commands do write out the tree they are working with to an
(in-memory or on-disk) index, so using the index this way would make a
warped kind of sense. But I agree that it is ugly.
> If anything, I'd
> like it if `check-attr' could just use the repository directly instead
> of the index (or a work tree) in a bare repository.
I think the right thing to do is to put this functionality in a new
‘git ls’ command. Maybe something like this:
$ git ls --format='%p %a(crlf)' master -- '*.txt'
some/path/foo.txt crlf:input
some/path/bar.txt crlf
some/path/other.txt !crlf
yet/another/path.txt
$
I can not promise I will find time before the weekend to work on it.
I wouldn’t be unhappy if someone else gets to it first.
Thanks for the explanations.
Jonathan
next prev parent reply other threads:[~2010-03-30 21:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 3:57 `git check-attr' problems & questions Eli Barzilay
2010-03-28 1:42 ` Jonathan Nieder
2010-03-29 15:28 ` Eli Barzilay
2010-03-29 16:09 ` Eli Barzilay
2010-03-29 23:15 ` git check-attr in bare repositories Jonathan Nieder
2010-03-30 4:53 ` Eli Barzilay
2010-03-30 21:22 ` Jonathan Nieder [this message]
2010-03-30 21:39 ` Jakub Narebski
2010-03-31 3:15 ` Eli Barzilay
2010-03-30 21:30 ` Carrying over attributes when moving files Jonathan Nieder
2010-03-31 3:30 ` Eli Barzilay
2010-03-31 4:05 ` 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=20100330212222.GA11192@progeny.tock \
--to=jrnieder@gmail.com \
--cc=eli@barzilay.org \
--cc=git@vger.kernel.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 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.