From: Nix <nix@esperi.org.uk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 12869@debbugs.gnu.org
Subject: bug#12869: 24.3.50; 'semantic-change-function' and incremental parsing broken by 'define-obsolete-variable-alias' problems
Date: Mon, 12 Nov 2012 19:01:59 +0000 [thread overview]
Message-ID: <87390e4pco.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <83a9umwujx.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 12 Nov 2012 20:22:10 +0200")
On 12 Nov 2012, Eli Zaretskii said:
>> From: Nix <nix@esperi.org.uk>
>> Emacs: because one operating system isn't enough.
>> Date: Mon, 12 Nov 2012 17:35:39 +0000
>> Cc: 12869@debbugs.gnu.org
>>
>> > I've changed the code (in emacs-24) to use the new name instead of the
>> > old one, which I believe should fix this problem.
>>
>> That means I need to learn enough about bzr to figure out how to get at
>> that change, doesn't it. I was hoping to avoid that, bzr makes my head
>> spin in a most unpleasant way.
>
> Like this:
>
> 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?
--
NULL && (void)
next prev parent reply other threads:[~2012-11-12 19:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 14:22 bug#12869: 24.3.50; 'semantic-change-function' and incremental parsing broken by 'define-obsolete-variable-alias' problems Nix
2012-11-12 14:36 ` bug#12869: This regression is not old Nix
2012-11-12 16:51 ` bug#12869: 24.3.50; 'semantic-change-function' and incremental parsing broken by 'define-obsolete-variable-alias' problems Stefan Monnier
2012-11-12 17:35 ` Nix
2012-11-12 18:22 ` Eli Zaretskii
2012-11-12 19:01 ` Nix [this message]
2012-11-12 19:15 ` Eli Zaretskii
2012-11-12 19:14 ` Glenn Morris
2012-11-12 19:15 ` Nix
2012-11-12 19:26 ` Nix
2012-11-12 21:09 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87390e4pco.fsf@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=12869@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.