Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> writes: >> Beyond, `--format=%(raw)` cannot be used with `--python`, `--shell`, >> `--tcl`, `--perl` because if our binary raw data is passed to a variable >> in the host language, the host language may not support arbitrary binary >> data in the variables of its string type. > > Perl at least deals with that just fine, and to the extent that it > doesn't any new problems here would have nothing to do with \0 being in > the data. Perl doesn't have a notion of "binary has \0 in it", it always > supports \0, it has a notion of "is it utf-8 or not?", so any encoding > problems wouldn't be new. I'd think that the same would be true of > Python, but I'm not sure. During an earlier iteration long time ago, as we knew Perl is capable of handling sequence of bytes including NUL, it was decided to start more strict by rejecting binary for all languages, which can later be loosened, to limit the scope of the initial implementation. >> + git hash-object blob1 -w | xargs git update-ref refs/myblobs/blob1 && >> + git hash-object blob2 -w | xargs git update-ref refs/myblobs/blob2 && >> + git hash-object blob3 -w | xargs git update-ref refs/myblobs/blob3 && >> + git hash-object blob4 -w | xargs git update-ref refs/myblobs/blob4 && >> + git hash-object blob5 -w | xargs git update-ref refs/myblobs/blob5 && >> + git hash-object blob6 -w | xargs git update-ref refs/myblobs/blob6 && >> + git hash-object blob7 -w | xargs git update-ref refs/myblobs/blob7 && >> + git hash-object blob8 -w | xargs git update-ref refs/myblobs/blob8 > > Hrm, xargs just to avoid: > > git update-ref ... $(git hash-object) ? That's horrible. Thanks for noticing. We'd want to catch segfaults from both hash-object and update-ref. One way to do so may be O=$(git hash-object -w blob1) && git update-ref refs/myblobs/blob1 "$O" Thanks for a review.
