GNU bug report logs - #12869
24.3.50; 'semantic-change-function' and incremental parsing broken by 'define-obsolete-variable-alias' problems

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Nix <nix <at> esperi.org.uk>
Cc: 12869 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca
Subject: bug#12869: 24.3.50; 'semantic-change-function' and incremental parsing broken by	'define-obsolete-variable-alias' problems
Date: Mon, 12 Nov 2012 21:15:42 +0200

> From: Nix <nix <at> esperi.org.uk>
> Cc: monnier <at> iro.umontreal.ca, 12869 <at> debbugs.gnu.org
> Emacs: more boundary conditions than the Middle East.
> Date: Mon, 12 Nov 2012 19:01:59 +0000
> 
> >   bzr log --line -l N  # shows the last N commits one per line
> >   bzr diff -c REVNO    # produces diffs for revision REVNO
> >
> > where REVNO is the number of the revision you find by looking at the
> > output of the first command.
> 
> Sure, that'll give me a log of the branch I'm on. But I'm on the trunk,
> not the emacs-24 branch -- can I really not get a log of the branch
> without waiting for hours as bzr pulls the whole thing down from
> upstream again? I mean, this branch is 99% the same as trunk: isn't
> there a way to reuse the revisions or something?

If you already have the trunk, pulling the branch should be fast,
because, as you point out, you already have most of the revisions.
Just be sure to do that under the same shared repository.  That is,
assuming you have emacs/trunk with the trunk and emacs is the
directory where you created the shared repository by "bzr init-repo",
then issue the "bzr branch" command under emacs to get the branch.

Previous Next

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