From: Stefan Monnier <monnier@iro•umontreal.ca>
To: git@vger•kernel.org
Subject: Re: fast-import fails in read-only tree
Date: Fri, 29 Jan 2016 09:28:44 -0500 [thread overview]
Message-ID: <jwv7fisxyhz.fsf-monnier+gmane.comp.version-control.git@gnu.org> (raw)
In-Reply-To: 20160129060802.GA23106@sigill.intra.peff.net
>> I recently discovered that "git fast-import" signals an error if used in
>> a tree to which we do not have write-access, because it tries to create
>> a "objects/pack/tmp_pack_XXX" file even before starting to process
>> the commands.
> The primary goal of fast-import is to write that packfile. It kind of
> sounds like you are using the wrong tool for the job.
Yes, I realize that. But in some cases it's the best tool available.
`fast-import' is very close to being a "generic access API" which can be
used instead of something like libgit. I think it'd be good to push it
yet a bit closer.
My earlier "cat-blob applied to a tree" issue is another such case.
> Can you elaborate on what you are sending to fast-import (preferably
> with a concrete example)?
I'm sending a stream of "progress <foo>; cat-blob <foo>", basically.
The concrete example is in [BuGit](https://gitlab.com/monnier/bugit),
see for example https://gitlab.com/monnier/bugit/commit/3678dcb8830a9c79c6f3404d75d63e6dd07bfe4c
> There may be a way to accomplish the same thing with read-only tools
> like cat-file.
Yes, I switched to using "cat-file --batch" instead, but it's less
convenient (I can't intersperse ad-hoc info in the output, the way I can
with "progress" in fast-import) and there are cases where the list of
files I need to extract cannot be determined without first looking at
some of those extracted files (I currently have been able to avoid
this in BuGit, luckily).
If I could use "cat-blob" on directories, there would be even more cases
where I'd want to use fast-import for read-only operations to reduce the
number of Git processes I fork.
Stefan
next prev parent reply other threads:[~2016-01-29 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 22:17 fast-import fails in read-only tree Stefan Monnier
2016-01-29 6:08 ` Jeff King
2016-01-29 14:28 ` Stefan Monnier [this message]
2016-01-30 5:13 ` Jeff King
2016-01-30 9:05 ` Andreas Schwab
2016-01-30 13:56 ` Stefan Monnier
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=jwv7fisxyhz.fsf-monnier+gmane.comp.version-control.git@gnu.org \
--to=monnier@iro$(echo .)umontreal.ca \
--cc=git@vger$(echo .)kernel.org \
/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