On Mon, 2008-09-29 at 23:14 +0000, Martin Pool wrote:
> John says:
>
> latest status is, we think we've fixed this, we can't reproduce this.
>
> Maybe we should close this for now?
From my aug 11 note on this:
What we need to do urgently:
- ensure commit rolls back the branch pointer if this happens so that
the problem commit doesn't get referenced
*** I don't recall getting this done.
- help the users affected to date recover
*** We did this
- get the workaround into distros using 1.3.1 (which seems to be common
version for this, could be 1.3.1 specific or more likely just that its
the version in hardy
*** I'm not sure we've made a push for this.
On Mon, 2008-09-29 at 23:14 +0000, Martin Pool wrote:
> John says:
>
> latest status is, we think we've fixed this, we can't reproduce this.
>
> Maybe we should close this for now?
From my aug 11 note on this:
What we need to do urgently:
- ensure commit rolls back the branch pointer if this happens so that
the problem commit doesn't get referenced
*** I don't recall getting this done.
- help the users affected to date recover
*** We did this
- get the workaround into distros using 1.3.1 (which seems to be common
version for this, could be 1.3.1 specific or more likely just that its
the version in hardy
*** I'm not sure we've made a push for this.
-Rob www.robertcolli ns.net/ keys.txt>.
--
GPG key available at: <http://