git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Graham Cox <graham@grahamcox.co.uk>
To: git@vger.kernel.org
Subject: git-archive for files changed in revision range
Date: Wed, 13 Feb 2008 13:03:04 +0000	[thread overview]
Message-ID: <20080213130304.GA19957@grahamcox.co.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]

Hiya,

We have a small project that is being managed in a Git repository (MSysGit to 
be exact) - mostly for backups and so on. The project is a mod for the 
computer game Civilization 4. (Actually a mod of a mod, but still...)  As 
such, to release the mod to other people to actually use the only thing that 
needs to be released is all of the files that have actually been changed. (The 
actual git repository contains ~700MB of files, the vast majority of which 
haven't changed since the initial import and so don't need to be downloaded by 
people).

I've managed to make it produce an archive that contains only the files that 
have changed by using a combination of git-archive and git-whatchanged, along 
with grep and sed, but it's kinda unwieldly. Is there a better way of doing 
this?

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.

-- 
Graham Cox


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

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

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

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=20080213130304.GA19957@grahamcox.co.uk \
    --to=graham@grahamcox.co.uk \
    --cc=git@vger.kernel.org \
    /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).