git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: demerphq <demerphq@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>,
	"Santi Béjar" <santi@agolina.net>, Git <git@vger.kernel.org>
Subject: 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?
Date: Fri, 31 Jul 2009 15:48:21 +0200	[thread overview]
Message-ID: <9b18b3110907310648y4178da4cs9264dc01de50426@mail.gmail.com> (raw)
In-Reply-To: <m3hbwtrpip.fsf@localhost.localdomain>

2009/7/31 Jakub Narebski <jnareb@gmail.com>:
> 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/"

  parent reply	other threads:[~2009-07-31 13:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29  8:15 Adding files to a git-archive when it is generated, and whats the best way to find out what branch a commit is on? demerphq
2009-07-29  8:40 ` 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 [this message]
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=9b18b3110907310648y4178da4cs9264dc01de50426@mail.gmail.com \
    --to=demerphq@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=rene.scharfe@lsrfire.ath.cx \
    --cc=santi@agolina.net \
    /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).