From: demerphq <demerphq@gmail.com>
To: Git <git@vger.kernel.org>
Subject: Adding files to a git-archive when it is generated, and whats the best way to find out what branch a commit is on?
Date: Wed, 29 Jul 2009 10:15:29 +0200 [thread overview]
Message-ID: <9b18b3110907290115v1f30eeat748631bb09f92517@mail.gmail.com> (raw)
I was wondering if anybody had any suggestions on a sane way to add a
file to a git-archive when it is being produced.
For instance build procedures that expect to be run inside of a git
WD wont work if built from an archived version of the tree. Being able
to provide a file of additional data to the archive package would be a
very convenient way to work around this.
Ideally id like to be able to specify a set of additional files to
include in the archive as part of the git-archive command line
interface, but I'd be nearly as a happy with almost any solution other
than the one I came up with, which is to use archive to generate a tar
file, then use tar to append the additional files to the tar, and then
compress it. This process turns out to be quite slow in comparison to
producing a compressed archive directly from git-archive.
Another question is whether anyone has any advice on the best way to
find out the "best" branch an arbitrary commit is on. Where best can
be flexibly definied to handle commits that are reachable from
multiple branches. I have hacked a solution involving git-log and
grep, but it performs quite poorly. I was wondering if there is a
better solution.
cheers,
Yves
--
perl -Mre=debug -e "/just|another|perl|hacker/"
next reply other threads:[~2009-07-29 8:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 8:15 demerphq [this message]
2009-07-29 8:40 ` Adding files to a git-archive when it is generated, and whats the best way to find out what branch a commit is on? Avery Pennarun
2009-07-29 8:41 ` Santi Béjar
2009-07-29 9:21 ` demerphq
2009-07-29 9:33 ` Santi Béjar
2009-07-29 9:51 ` demerphq
2009-07-29 11:13 ` Santi Béjar
2009-07-30 20:33 ` René Scharfe
2009-07-31 10:04 ` demerphq
[not found] ` <m3hbwtrpip.fsf@localhost.localdomain>
2009-07-31 13:48 ` demerphq
2009-08-02 13:52 ` René Scharfe
2009-08-02 14:19 ` demerphq
2009-08-04 17:50 ` René Scharfe
2009-07-29 16:12 ` Jeff Epler
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=9b18b3110907290115v1f30eeat748631bb09f92517@mail.gmail.com \
--to=demerphq@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).