Thomas Rast <trast@xxxxxxxxxxxxxxx> writes:
>> But
>>
>> $ time git branch -r --contains next
>> github2/next
>> gph/next
>> ko/next
>> repo/next
>>
>> real 0m3.853s
[...]
> I'll get rid of all this cruft now, but this command doesn't scale in
> the direction I'm abusing it :-)
BTW, my original point still stands: at nearly 4s per invocation of
'branch -r --contains', the loop as written by Lucien
> +add_remoterefs () {
> + while read -r command sha1 message
> + do
> + printf '%s\n' "$command $sha1 $message"
> + git branch -r --contains "$sha1" >"$1.branch"
[...]
> + done >"$1.published" <"$1"
> + cat "$1.published" >"$1"
> + rm -f "$1.published" "$1.branch"
> +}
is unusable in your repository, too. Which is a real pity, it's a nice
idea.
--
Thomas Rast
trast@{inf,student}.ethz.ch
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html