2011/5/12 Michal Marek <mmarek@xxxxxxx>:
> On 12.5.2011 20:25, mfmooney@xxxxxxxxx wrote:
>> diff --git a/scripts/package/Makefile b/scripts/package/Makefile
>> index 1b7eaea..a32dc2d 100644
>> --- a/scripts/package/Makefile
>> +++ b/scripts/package/Makefile
>> @@ -118,10 +118,14 @@ perf-tar=perf-$(KERNELVERSION)
>>
>> quiet_cmd_perf_tar = TAR
>> cmd_perf_tar = \
>> -git archive --prefix=$(perf-tar)/ HEAD^{tree} \
>> - $$(cat $(srctree)/tools/perf/MANIFEST) -o $(perf-tar).tar; \
>> +git --git-dir=$(srctree)/.git --work-tree=$(srctree) \
>
> Neither git archive not git rev-parse need the work tree, --git-dir=..
> is sufficient.
Are you sure? --git-dir points to the .git directory and --work-tree
points to the actual source code directory. Both are needed when you
are out of the source tree and the .git directory is not really
located at .git from the $PWD.
>From an empirical standpoint, this as well as any git command that is
issued from outside of the working directory fails to function
properly without --work-tree.
-matt
>
>> + archive --prefix=$(perf-tar)/ HEAD^{tree} \
>> + $(addprefix $(srctree)/, \
>> + $(shell cat $(srctree)/tools/perf/MANIFEST)) \
>> + -o $(perf-tar).tar; \
>> mkdir -p $(perf-tar); \
>> -git rev-parse HEAD > $(perf-tar)/HEAD; \
>> +git --git-dir=$(srctree)/.git --work-tree=$(srctree) \
>> + rev-parse HEAD > $(perf-tar)/HEAD; \
>> tar rf $(perf-tar).tar $(perf-tar)/HEAD; \
>> rm -r $(perf-tar); \
>> $(if $(findstring tar-src,$@),, \
>
>
--
GPG-Key: 9AFE00EA
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
