From: Robert Clausecker <fuzxxl@gmail.com>
To: git@vger.kernel.org
Subject: Feature request: Allow extracting revisions into directories
Date: Sun, 03 Feb 2013 15:18:05 +0100 [thread overview]
Message-ID: <1359901085.24730.11.camel@t520> (raw)
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
Hello!
git currently has the archive command that allows to save an arbitrary
revision into a tar or zip file. Sometimes it is useful to not save this
revision into an archive but to directly put all files into an arbitrary
directory. Currently this seems to be not possible to archive directly;
the only way I found to do it is to run git archive and then directly
unpack the archive into a directory.
git --git-dir REPO archive REVISION | tar x
It would be nice to have a command or simply a switch to git archive
that allows the user to put the files of REVISION into a directory
instead of making an archive.
Thank you very much for your help. Yours,
Robert Clausecker
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2013-02-03 14:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 14:18 Robert Clausecker [this message]
2013-02-03 16:25 ` Feature request: Allow extracting revisions into directories Sitaram Chamarty
2013-02-03 18:11 ` Robert Clausecker
2013-02-04 0:42 ` Sitaram Chamarty
2013-02-05 15:11 ` Phil Hord
2013-02-09 15:58 ` Robert Clausecker
2013-02-09 23:00 ` Junio C Hamano
2013-02-10 3:45 ` Junio C Hamano
2013-02-10 3:57 ` Robert Clausecker
2013-02-10 4:06 ` Jonathan Nieder
2013-02-10 4:10 ` Robert Clausecker
2013-02-10 4:19 ` Jonathan Nieder
2013-02-03 23:26 ` Konstantin Khomoutov
2013-02-04 11:18 ` Michael J Gruber
2013-02-04 12:14 ` Robert Clausecker
2013-02-04 12:47 ` Tomas Carnecky
2013-02-04 16:52 ` Junio C Hamano
2013-02-05 8:55 ` Sitaram Chamarty
2013-02-04 12:58 ` Andrew Ardill
2013-02-04 16:55 ` Junio C Hamano
2013-02-04 18:21 ` Andreas Schwab
2013-02-10 12:16 ` Thomas Koch
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=1359901085.24730.11.camel@t520 \
--to=fuzxxl@gmail.com \
--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).