Re: [PATCH v2 3/3] send-pack: assign remote errors to each ref

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Jeff King
Date: Wednesday, November 14, 2007 - 9:54 pm

On Wed, Nov 14, 2007 at 02:01:14AM +0000, Johannes Schindelin wrote:


Oops, I'm clearly an idiot. I explicitly looked at bad_ref_char before
writing the original message, and somehow read that as strictly less
than.

So the parsing problem goes away, and I think using the sort order as a
hint takes away the potential performance problem (I don't even know if
it was a problem -- there may be other O(n^2) behavior).

I will take a look at the tests Alex has been working on, maybe add a
few to it, and submit a cleaned-up series.

-Peff
-
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
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[RFC/PATCH 0/3] tracking per-ref errors on push, Jeff King, (Tue Nov 13, 3:25 am)
Re: [RFC/PATCH 0/3] tracking per-ref errors on push, Jeff King, (Tue Nov 13, 4:34 am)
[PATCH v2 1/3] send-pack: track errors for each ref, Jeff King, (Tue Nov 13, 4:36 am)
Re: [PATCH v2 3/3] send-pack: assign remote errors to each ref, Johannes Schindelin, (Tue Nov 13, 7:01 pm)
Re: [PATCH v2 3/3] send-pack: assign remote errors to each ref, Jeff King, (Wed Nov 14, 9:54 pm)