Re: Adding files to a git-archive when it is generated, and whats the best way to find out what branch a commit is on?
- From
- demerphq <demerphq@gmail.com>
- Date
- Jul 31, 2009, 13:48 UTC
- Message-ID
- <9b18b3110907310648y4178da4cs9264dc01de50426@mail.gmail.com>
- In-Reply-To
- <m3hbwtrpip.fsf@localhost.localdomain>
2009/7/31 Jakub Narebski <jnareb@gmail.com>:
Show 35 quoted lines
> demerphq <demerphq@gmail.com> writes: >> 2009/7/30 René Scharfe <rene.scharfe@lsrfire.ath.cx>: >> > demerphq schrieb: > >>>> So then git also would benefit from support in git-archive for adding >>>> arbitrary files to the archive during generation? >>> >>> Yes, and this has come up before. >>> >>> How about the following? It's missing documentation and a test case, >>> but you could try >>> >>> $ git archive --add-file extra HEAD>HEAD+extra.tar >>> >>> or >>> >>> $ git archive --prefix=a/ --add-file extra --prefix=b/ HEAD>ba.tar >> >> I havent managed to try it out yet but this is pretty much exactly >> what I was looking for. Only thought I had was that it might be nice >> to be able to specify what name the file should be added as so that >> you can add files to subpaths deeper than the root/root prefix of the >> tar. However for /my/ particular purposes that is unnecessary, it only >> occurs to me as a nice to have. But if you were inclined to think >> about extending it I was thinking an argument notation like --add-file >> foo:bar/baz/bop might be useful. > > Why not use notation used by --graft-points option of mkisofs, i.e. > "--add-file foo=bar/baz/bop", where 'foo' is name in archive > (respective to prefix if any, I think), and 'bar/baz/bop' is name in > filesystem. > > The proposed notation "--add-file foo:bar/baz/bop" looks for me (see > extended sha-1 syntax in git-rev-parse manpage) like adding file > 'bar/baz/bop' from 'foo' tree-ish.
Whatever is most appropriate. I was just demonstrating what I had in mind.
cheers, Yves
-- perl -Mre=debug -e "/just|another|perl|hacker/"