Passing tar(1) options via git-archive(1)

2014-09-23 Thread Daniel Brockman
Some background from the git-archive(1) man page: git-archive behaves differently when given a tree ID versus when given a commit ID or tag ID. In the first case the current time is used as the modification time of each file in the archive. In the latter case the commit time as

Re: Passing tar(1) options via git-archive(1)

2014-09-23 Thread Thomas Braun
Am 23.09.2014 um 20:57 schrieb Daniel Brockman: Some background from the git-archive(1) man page: git-archive behaves differently when given a tree ID versus when given a commit ID or tag ID. In the first case the current time is used as the modification time of each file in the

Re: Passing tar(1) options via git-archive(1)

2014-09-23 Thread brian m. carlson
On Tue, Sep 23, 2014 at 11:49:24PM +0200, Thomas Braun wrote: Am 23.09.2014 um 20:57 schrieb Daniel Brockman: Would it make sense to add an --mtime option to git-archive(1) to enable explicitly setting the mtime for all files in the archive? It could just pass through to the tar(1) --mtime

Re: Passing tar(1) options via git-archive(1)

2014-09-23 Thread Daniel Brockman
brian m. carlson sand...@crustytoothpaste.net writes: Git does not invoke tar(1). It has its own tar (actually, pax) implementation, so any options would have to be implemented in Git. We'd probably want to make such a change effective in the zip format as well. Ah, I see... Well, I guess

Re: Passing tar(1) options via git-archive(1)

2014-09-23 Thread Jeff King
On Wed, Sep 24, 2014 at 03:26:22AM +0200, Daniel Brockman wrote: brian m. carlson sand...@crustytoothpaste.net writes: Git does not invoke tar(1). It has its own tar (actually, pax) implementation, so any options would have to be implemented in Git. We'd probably want to make such a