From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: mfmooney@gmail.com
Cc: Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v3] package: Makefile: fix perf target bug
Date: Sun, 15 May 2011 15:40:02 +0000 [thread overview]
Message-ID: <20110515154002.GB6274@ghostprotocols.net> (raw)
In-Reply-To: <b07e7ecdce48bc90a2cf83e8867494dae7cd174f.1305329845.git.mfm@muteddisk.com>
Em Fri, May 13, 2011 at 04:41:12PM -0700, mfmooney@gmail.com escreveu:
> From: matt mooney <mfm@muteddisk.com>
>
> Specify --git-dir when building perf targets to allow out-of-tree
> builds using O=<build-dir>.
>
> The shell command in `git archive' had to be modified to allow proper
> file name expansion of the files listed in MANIFEST.
>
> Signed-off-by: matt mooney <mfm@muteddisk.com>
Michal,
Can I have your Reviewed-by or Acked-by for this one? Assuming
all is ok by now :)
- Arnaldo
WARNING: multiple messages have this Message-ID (diff)
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: mfmooney@gmail.com
Cc: Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v3] package: Makefile: fix perf target bug
Date: Sun, 15 May 2011 12:40:02 -0300 [thread overview]
Message-ID: <20110515154002.GB6274@ghostprotocols.net> (raw)
In-Reply-To: <b07e7ecdce48bc90a2cf83e8867494dae7cd174f.1305329845.git.mfm@muteddisk.com>
Em Fri, May 13, 2011 at 04:41:12PM -0700, mfmooney@gmail.com escreveu:
> From: matt mooney <mfm@muteddisk.com>
>
> Specify --git-dir when building perf targets to allow out-of-tree
> builds using O=<build-dir>.
>
> The shell command in `git archive' had to be modified to allow proper
> file name expansion of the files listed in MANIFEST.
>
> Signed-off-by: matt mooney <mfm@muteddisk.com>
Michal,
Can I have your Reviewed-by or Acked-by for this one? Assuming
all is ok by now :)
- Arnaldo
next prev parent reply other threads:[~2011-05-15 15:40 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 ` [Resend PATCH] " Michal Marek
2011-05-13 8:26 ` 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 [this message]
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=20110515154002.GB6274@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfmooney@gmail.com \
--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 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.