From: Junio C Hamano <gitster@pobox•com>
To: Jeff King <peff@peff•net>
Cc: Duy Nguyen <pclouds@gmail•com>,
Graeme Geldenhuys <mailinglists@geldenhuys•co.uk>,
git@vger•kernel.org
Subject: Re: Git archiving only branch work
Date: Thu, 13 Nov 2014 13:10:17 -0800 [thread overview]
Message-ID: <xmqqvbmizu12.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20141113200640.GB3869@peff.net> (Jeff King's message of "Thu, 13 Nov 2014 15:06:40 -0500")
Jeff King <peff@peff•net> writes:
> On Thu, Nov 13, 2014 at 08:36:16PM +0700, Duy Nguyen wrote:
>
>> On Thu, Nov 13, 2014 at 12:32:40PM +0000, Graeme Geldenhuys wrote:
>> > [alias]
>> > deploy = !sh -c 'git archive --prefix=$1/ -o deploy_$1.zip HEAD
>> > $(git diff --name-only -D $2)' -
>> >
>> > This works very well. The only problem we have so far is that if we
>> > have files with spaces in the name (eg: SQL update scripts), then the
>> > command breaks.
>> >
>> > Does anybody have an idea on how this can be resolved? Any help would
>> > be much appreciated.
>>
>> I wonder if it's overkill to do something like this patch ("git
>> archive" may need some more updates for it to work though). With it
>> you can do:
>>
>> git diff --name-only ... | git archive ... HEAD -- ":(file)-"
>>
>> The good thing is it works for other commands as well. But is it
>> really a good thing..
>
> I like the idea of taking paths from stdin (and especially if there is a
> "-z" option). But using a pathspec that reads from stdin seems like it
> creates a lot of corner cases. What would:
>
> git rev-list --stdin -- ":(file)-"
>
> do? It is kind of neat that you could read from multiple files (besides
> stdin), but I'm not sure it is all that useful in practice (you can
> always cat them to its stdin).
>
> How about just adding --stdin, which matches other git commands?
How about doing nothing and use the correct $IFS instead?
next prev parent reply other threads:[~2014-11-13 21:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 12:32 Git archiving only branch work Graeme Geldenhuys
2014-11-13 13:19 ` Peter Krefting
2014-11-13 13:36 ` Duy Nguyen
2014-11-13 16:49 ` Junio C Hamano
2014-11-13 20:06 ` Jeff King
2014-11-13 21:10 ` Junio C Hamano [this message]
2014-11-13 21:33 ` Jeff King
2014-11-13 21:36 ` Junio C Hamano
2014-11-13 21:39 ` Jeff King
2014-11-13 21:48 ` Junio C Hamano
2014-11-14 15:32 ` Jeff King
2014-11-14 20:35 ` Junio C Hamano
2014-11-13 16:10 ` Thomas Koch
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=xmqqvbmizu12.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=mailinglists@geldenhuys$(echo .)co.uk \
--cc=pclouds@gmail$(echo .)com \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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