From: Michal Marek <mmarek@suse.cz>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: "Sam Ravnborg" <sam@ravnborg.org>,
"David S. Miller" <davem@davemloft.net>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Ingo Molnar" <mingo@elte.hu>, "Mike Galbraith" <efault@gmx.de>,
"Paul Mackerras" <paulus@samba.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Stephane Eranian" <eranian@google.com>,
"Tom Zanussi" <tzanussi@gmail.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] perf tools: Make target to generate self contained source tarball
Date: Mon, 31 May 2010 22:11:24 +0200 [thread overview]
Message-ID: <4C0417EC.8050906@suse.cz> (raw)
In-Reply-To: <20100531174207.GB3481@ghostprotocols.net>
On 31.5.2010 19:42, Arnaldo Carvalho de Melo wrote:
> +git archive --prefix=$(perf-tar)/ HEAD^{tree} \
If you use plain "HEAD" (a commit-ish) instead if HEAD^{tree}, then
git archive will store the commit id in the archive metadata and the
user can then use git get-tar-commit-id to extract it.
> + $$(cat $(srctree)/tools/perf/MANIFEST) -o $(perf-tar).tar; \
> +mkdir -p $(perf-tar); \
> +git rev-parse HEAD > $(perf-tar)/HEAD; \
> +tar rf $(perf-tar).tar $(perf-tar)/HEAD; \
... then this HEAD file might not even be necessary (even if you keep
it, it would be nice not to break git get-tar-commit-id).
Michal
next prev parent reply other threads:[~2010-05-31 20:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 18:53 [PATCH 1/1] perf tools: Make target to generate self contained source tarball Arnaldo Carvalho de Melo
2010-05-29 7:29 ` Sam Ravnborg
2010-05-29 13:40 ` Arnaldo Carvalho de Melo
2010-05-31 15:42 ` Arnaldo Carvalho de Melo
2010-05-31 17:42 ` [PATCH v2 " Arnaldo Carvalho de Melo
2010-05-31 18:06 ` Sam Ravnborg
2010-05-31 20:11 ` Michal Marek [this message]
2010-05-31 23:06 ` Arnaldo Carvalho de Melo
2010-06-01 10:28 ` Michal Marek
2010-06-04 17:35 ` Arnaldo Carvalho de Melo
2010-06-07 10:11 ` 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=4C0417EC.8050906@suse.cz \
--to=mmarek@suse.cz \
--cc=acme@infradead.org \
--cc=davem@davemloft.net \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=sam@ravnborg.org \
--cc=tzanussi@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.