From: Eli Barzilay <eli@barzilay.org>
To: Jonathan Nieder <jrnieder@gmail.com>, git@vger.kernel.org
Subject: Re: `git check-attr' problems & questions
Date: Mon, 29 Mar 2010 12:09:15 -0400 [thread overview]
Message-ID: <19376.53419.640007.930897@winooski.ccs.neu.edu> (raw)
In-Reply-To: <19376.50971.397375.810974@winooski.ccs.neu.edu>
On Mar 29, Eli Barzilay wrote:
> On Mar 27, Jonathan Nieder wrote:
> > : "Usage: $0 commit check-attr-args" &&
> >
> > GIT_INDEX=tmp-index git read-tree --reset -i "$1" &&
> > shift &&
> > GIT_INDEX=tmp-index git check-attr "$@" &&
> > rm tmp-index
>
> I tried that, but it doesn't work. (I used GIT_INDEX_FILE.)
In case I'm doing something wrong, here's a script that shows the
problem that I have:
#!/bin/sh
rm -rf /tmp/test
mkdir /tmp/test
cd /tmp/test
mkdir t
cd t
git init > /dev/null
echo "Blah" > foo
echo "foo x=y" > .gitattributes
git add foo .gitattributes
git commit -m "stuff" > /dev/null
echo -n "check-attr in a working directory: "
git check-attr x foo
cd ..
git clone --bare t > /dev/null
cd t.git
git read-tree --reset -i master
echo -n "check-attr in a bare repository: "
git check-attr x foo
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
next prev parent reply other threads:[~2010-03-29 16:09 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 [this message]
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
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=19376.53419.640007.930897@winooski.ccs.neu.edu \
--to=eli@barzilay.org \
--cc=git@vger.kernel.org \
--cc=jrnieder@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).