From: matt mooney <mfmooney@gmail.com>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [Resend PATCH] package: Makefile: fix perf target bug
Date: Fri, 13 May 2011 11:52:38 -0700 [thread overview]
Message-ID: <BANLkTimcs83J3O8o7npLftBaQk1WKKZ=2Q@mail.gmail.com> (raw)
In-Reply-To: <4DCCEB48.7030602@suse.cz>
On Fri, May 13, 2011 at 1:26 AM, Michal Marek <mmarek@suse.cz> wrote:
> On 12.5.2011 23:38, matt mooney wrote:
>>
>> On Thu, May 12, 2011 at 2:20 PM, Michal Marek<mmarek@suse.cz> wrote:
>>>
>>> On 12.5.2011 23:07, matt mooney wrote:
>>>>
>>>> 2011/5/12 Michal Marek<mmarek@suse.cz>:
>>>>>
>>>>> Neither git archive not git rev-parse need the work tree, --git-dir=..
>>>>> is sufficient.
>>>>
>>>> Are you sure?
>>>
>>> Yes.
>>> $ cd /tmp
>>> $ git --git-dir=$HOME/linux-2.6/.git rev-parse HEAD
>>> e0a04b11e4059cab033469617c2a3ce2d8cab416
>>>
>>
>> You are right about that command, but it doesn't use the source tree.
>
> Yes, neither git rev-parse nor git archive use the work tree. That's what I
> tried to explain to you in my first mail.
Okay, again you are right; I erroneously thought git archive needed
the work tree too.
>> Do a git --git-dir=$HOME/linux-2.6/.git status from /tmp and see what
>> happens.
>
> That's irrelevant, I only talked about archive and rev-parse.
>
>
>> So do you want me to send a new patch without --work-tree= in git
>> rev-parse?
>
> And in git archive.
So the real problem is that tools/perf/MANIFEST contains wildcards,
and when git archive is run, file name expansion isn't working
properly. By adding the $(srctree) as a prefix, globbing works but
then git archive requires --work-tree to be set.
I really don't know of a better alternative.
Thanks,
matt
--
GPG-Key: 9AFE00EA
next prev parent reply other threads:[~2011-05-13 18:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 18:25 mfmooney
2011-05-12 20:30 ` Michal Marek
2011-05-12 21:07 ` matt mooney
2011-05-12 21:20 ` Michal Marek
2011-05-12 21:38 ` matt mooney
2011-05-13 0:09 ` [PATCH v2] " mfmooney
2011-05-13 8:26 ` [Resend PATCH] " Michal Marek
2011-05-13 18:52 ` matt mooney [this message]
2011-05-13 19:56 ` Michal Marek
2011-05-13 23:26 ` matt mooney
2011-05-13 23:41 ` [PATCH v3] " mfmooney
2011-05-15 15:40 ` Arnaldo Carvalho de Melo
2011-05-16 8:19 ` Michal Marek
2011-06-12 18:19 ` matt mooney
2011-06-24 13:22 ` Michal Marek
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='BANLkTimcs83J3O8o7npLftBaQk1WKKZ=2Q@mail.gmail.com' \
--to=mfmooney@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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
Powered by JetHome