Re: Malformed branch name in fast-export when specifying non-HEAD/branch revision

From: Sverre Rabbelier <srabbelier@gmail.com>
Date: Aug 22, 2011, 18:05 UTC
Message-ID: <CAGdFq_hU3EnZnBh_eb7uax_Cb=0eA1K3GxMys+S60SEm94UE1w@mail.gmail.com>
In-Reply-To: <20110822175705.GB1945@sigill.intra.peff.net>

Heya,

On Mon, Aug 22, 2011 at 10:57, Jeff King <peff@peff.net> wrote:

Show 5 quoted lines

> I just read through the remote-helper threads from early June, and the
> only mention of triggering that is when you actually have a rename
> (i.e., your "refs/heads/foo" becomes remote's "refs/heads/bar", but we
> mention "refs/heads/foo" in the export stream). I was thinking there was
> another case, but I couldn't find mention of it.

The patches Dscho and I sent are in response to the RFC patches (that are currently "stalled" in whats-cooking) I added on top of the series that rerolled yours.

> Yeah, the behavior of your patch looks fine to me. I thought the point
> in contention was that having export understand refspecs would fix a lot
> of _other_ cases, too.

Right. Sadly it doesn't look like I'll have time to try and fix 'git bundle' anytime soon, so this'll remain broken.

-- 
Cheers,

Sverre Rabbelier