git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Graham Cox <graham@grahamcox.co.uk>
Cc: git@vger.kernel.org
Subject: Re: git-archive for files changed in revision range
Date: Wed, 13 Feb 2008 14:43:23 +0100	[thread overview]
Message-ID: <47B2F3FB.3020600@viscovery.net> (raw)
In-Reply-To: <20080213130304.GA19957@grahamcox.co.uk>

Graham Cox schrieb:
> The command line I used was something like (This is mostly from memory):
> git-archive --format=zip . `git-whatchanged <start>..HEAD --pretty=oneline 
>   | grep '^:' | sed 's/^.*\t//'` > release.zip
> 
> To produce a zip containing all of the modified and added files for the 
> revision range <start>..HEAD.

git diff-tree -r --name-only -z <start> HEAD | \
    xargs -0 git archive --format=zip HEAD > release.zip

-- Hannes

      parent reply	other threads:[~2008-02-13 13:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13 13:03 git-archive for files changed in revision range Graham Cox
2008-02-13 13:37 ` Johannes Schindelin
2008-02-13 13:43 ` Jeff King
2008-02-13 13:43 ` Johannes Sixt [this message]

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=47B2F3FB.3020600@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=git@vger.kernel.org \
    --cc=graham@grahamcox.co.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).