I debated that, it seemed a wash but can do.
Patches gratefully accepted for that. This exceeds my skills in bash: I
can do that in python, C, or other languages, but in bash I am working
through a list that is a part of $* an arg at a time with no ability to
look at the next, which is what this needs. Unless of course bash arrays
are part of portable shell (not sure on that).
Originally, this was in python with zip file built in memory (no
temporaries). Sticking to portable shell makes many easy things really
hard. I'll think about this.
Good idea, but I think it is simpler to just keep the ^... output from
git-rev-parse and check that those exist. What you suggest below seems
to presume all bases are themselves references, which is not the case
when doing, for example, master~10..master.
I have to say I do not understand what "mark them as shallow" means: can
you please enlighten me further?
Thanks,
Mark
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html