Re: [Resend PATCH] package: Makefile: fix perf target bug

All of lore.kernel.org
 help / color / mirror / Atom feed

From: Michal Marek <mmarek@suse.cz>
To: matt mooney <mfmooney@gmail.com>
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 08:26:48 +0000	[thread overview]
Message-ID: <4DCCEB48.7030602@suse.cz> (raw)
In-Reply-To: <BANLkTimrW=ZG2sGG1Q8QehSnh5rW1eBzGw@mail.gmail.com>

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.


> 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.

Michal

WARNING: multiple messages have this Message-ID (diff)

From: Michal Marek <mmarek@suse.cz>
To: matt mooney <mfmooney@gmail.com>
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 10:26:48 +0200	[thread overview]
Message-ID: <4DCCEB48.7030602@suse.cz> (raw)
In-Reply-To: <BANLkTimrW=ZG2sGG1Q8QehSnh5rW1eBzGw@mail.gmail.com>

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.


> 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.

Michal

next prev parent reply	other threads:[~2011-05-13  8:26 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12 18:25 [Resend PATCH] package: Makefile: fix perf target bug mfmooney
2011-05-12 18:25 ` mfmooney
2011-05-12 20:30 ` Michal Marek
2011-05-12 20:30   ` Michal Marek
2011-05-12 21:07   ` matt mooney
2011-05-12 21:07     ` matt mooney
2011-05-12 21:07     ` matt mooney
2011-05-12 21:20     ` Michal Marek
2011-05-12 21:20       ` Michal Marek
2011-05-12 21:38       ` matt mooney
2011-05-12 21:38         ` matt mooney
2011-05-13  0:09         ` [PATCH v2] " mfmooney
2011-05-13  0:09           ` mfmooney
2011-05-13  5:22           ` WANG Cong
2011-05-13  8:26         ` Michal Marek [this message]
2011-05-13  8:26           ` [Resend PATCH] " Michal Marek
2011-05-13 18:52           ` matt mooney
2011-05-13 18:52             ` matt mooney
2011-05-13 19:56             ` Michal Marek
2011-05-13 19:56               ` Michal Marek
2011-05-13 23:26               ` matt mooney
2011-05-13 23:26                 ` matt mooney
2011-05-13 23:41               ` [PATCH v3] " mfmooney
2011-05-13 23:41                 ` mfmooney
2011-05-15 15:40                 ` Arnaldo Carvalho de Melo
2011-05-15 15:40                   ` Arnaldo Carvalho de Melo
2011-05-16  8:19                   ` Michal Marek
2011-05-16  8:19                     ` Michal Marek
2011-06-12 18:19                     ` matt mooney
2011-06-12 18:19                       ` matt mooney
2011-06-24 13:22                       ` Michal Marek
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=4DCCEB48.7030602@suse.cz \
    --to=mmarek@suse.cz \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfmooney@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 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.