git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Mr. Meitar Moscovitz" <meitarm@gmail.com>
To: git@vger.kernel.org
Subject: Archiving a git superproject and all of its submodules: git-archive-all.sh
Date: Sat, 23 Aug 2008 20:50:21 +1000	[thread overview]
Message-ID: <07897A4C-B639-44AB-8E52-4873CA0D1136@gmail.com> (raw)

Hi all,

First-time poster, relatively green git user (I switched from  
Subversion about three months ago). So please don't bite…yet. :)

A co-worker wanted an easy way to archive a git superproject and all  
of its submodules (if any), so I created a shell script to do just  
that after being inspired by a message that I think was posted to this  
list and unfortunately can no longer find. The script is pretty simple  
(by which I mean it's probably kind of stupid), but it is a generic  
solution and it seems to do the job well. My team has been using it  
internally to  create deployment-ready tarballs that includes all the  
code of our (super)project and its dependent code in the git submodules.

If anyone is so inclined, I'd love some feedback on the script. I'm  
hosting it under the name "git-archive-all.sh" on Github:

http://github.com/meitar/git-archive-all.sh/wikis

The script has a few things I think are at least a little interesting.  
For instance, by default it creates a "super archive" of the project,  
but it can also be told to produce separate archives for each git repo  
(by passing a --separate option), and you can pass the --prefix option  
just as you can with git-archive, among other things.

Anyway, I hope someone finds this useful at some point.

Kind regards,
--
-Meitar Moscovitz
Personal: http://maymay.net
Professional: http://MeitarMoscovitz.com

                 reply	other threads:[~2008-08-23 10:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=07897A4C-B639-44AB-8E52-4873CA0D1136@gmail.com \
    --to=meitarm@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).