From: Pierre Habouzit <madcoder@madism.org>
To: rene.scharfe@lsrfire.ath.cx
Cc: git@vger.kernel.org
Subject: [wishlist] git-archive -L
Date: Mon, 02 Feb 2009 15:34:25 +0100 [thread overview]
Message-ID: <20090202143425.GA30667@artemis.corp> (raw)
[-- Attachment #1: Type: text/plain, Size: 1596 bytes --]
Hi Rene,
I wanted to do that myself, but I sadly miss the time right now, so I
wonder if you'd know how to do the following.
We have in our repository a kind of modular system (for a family of web
sites) where each web-site uses a (versionned) symlink farm. IOW it
works basically that way:
www/module1
www/module2
product_A/www/module1 -> ../../www/module1
product_A/www/module_A
product_B/www/module1 -> ../../www/module1
product_B/www/module2 -> ../../www/module2
product_B/www/module_B
Though product_A and _B even if they share a fair amount of code, are
separate products and when we release, we'd like to be able to perform
from inside:
git archive --format=tar -L product_$A
where -L basically does what it does in cp: dereference symlinks. To
make the thing hairier, we also have symlinks _inside_ www/ (pointing
into the same subtree) that we'd like to keep if possible (even if it's
not a big deal).
So I'd suggest something where -L only dereferences the symlink if it
goes outside of the list of paths passed to git-archive, and -LL (or -L
-L) dereferences anything. Of course this would only make sense if the
symlinks resolve to something that is tracked :)
For now we git archive the whole repository, use tar xh; rm what we
don't like, reset the symlinks we want to keep, and retar, which is kind
of counterproductive :)
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-02-02 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 14:34 Pierre Habouzit [this message]
2009-02-03 8:10 ` [wishlist] git-archive -L René Scharfe
2009-02-04 23:00 ` René Scharfe
2009-02-05 15:04 ` Pierre Habouzit
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=20090202143425.GA30667@artemis.corp \
--to=madcoder@madism.org \
--cc=git@vger.kernel.org \
--cc=rene.scharfe@lsrfire.ath.cx \
/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).