unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: chad <yandros@MIT.EDU>
Cc: 12193@debbugs.gnu.org, ueno@unixuser.org
Subject: bug#12193: 24.1.50; 24.1.50; Completion broken in revno 109116
Date: Tue, 14 Aug 2012 18:41:41 +0300	[thread overview]
Message-ID: <83lihhjxai.fsf@gnu.org> (raw)
In-Reply-To: <078C7F77-D79A-4B6F-AD27-5078DEB53BED@mit.edu>

> From: chad <yandros@MIT.EDU>
> Date: Mon, 13 Aug 2012 20:29:22 -0700
> Cc: 12193@debbugs.gnu.org
> 
> On 13 Aug 2012, at 19:50, Eli Zaretskii <eliz@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.





  reply	other threads:[~2012-08-14 15:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 18:23 bug#12193: 24.1.50; 24.1.50; Completion broken in revno 109116 chad
2012-08-13 19:16 ` Eli Zaretskii
2012-08-13 21:04   ` chad
2012-08-14  2:50     ` Daiki Ueno
2012-08-14  3:19       ` Daiki Ueno
2012-08-14  3:29         ` chad
2012-08-14 15:41           ` Eli Zaretskii [this message]
2012-08-14 15:59             ` chad
2012-08-14  4:37       ` Chong Yidong
2012-08-14  2:50     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83lihhjxai.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=12193@debbugs.gnu.org \
    --cc=ueno@unixuser.org \
    --cc=yandros@MIT.EDU \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).