GNU bug report logs - #12193
24.1.50; 24.1.50; Completion broken in revno 109116

Previous Next

Full log

Message #31 received at 12193 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: chad <yandros <at> MIT.EDU>
Cc: 12193 <at> debbugs.gnu.org, ueno <at> unixuser.org
Subject: Re: bug#12193: 24.1.50; 24.1.50; Completion broken in revno 109116
Date: Tue, 14 Aug 2012 18:41:41 +0300

> From: chad <yandros <at> MIT.EDU>
> Date: Mon, 13 Aug 2012 20:29:22 -0700
> Cc: 12193 <at> debbugs.gnu.org
> 
> On 13 Aug 2012, at 19:50, Eli Zaretskii <eliz <at> gnu.org> wrote:
> 
> >> With this recipe, it still happens in revno 109117.
> > 
> > Which is 500 revisions old.  Maybe you should resync.
> 
> I wonder if this is a bazaar numbering issue? My first report was from a sync that was less than an hour old; the second was less than 5 minutes old. I do have a few private patches on that branch, so maybe that's my fault?  I'm a bazaar novice.

If your branch is not bound to the upstream branch, then revision
numbers are useless, because they have no relation to the trunk.  You
should then use revision-ids, not revnos.

> P.S. I'll admit to being amused that my report mentioned that the cursor was in the wrong window, and I got the reply ``but the cursor shouldn't be in that window''. :-)

I never said anything like that.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.