From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: 13708@debbugs.gnu.org
Subject: bug#13708: 24.3.50; icomplete, ido, iswitchb: Replace C-s, C-r with C-. and C-,
Date: Fri, 15 Feb 2013 18:40:14 -0500 [thread overview]
Message-ID: <jwvmwv5176h.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87621te3um.fsf@gmail.com> (Jambunathan K.'s message of "Sat, 16 Feb 2013 01:39:37 +0530")
>>> I am proposing C-, and C-. as useful defaults.
>>> For fear of resentment, I am leaving C-s and C-r bindings intact.
>>> Reviewer may delete them at his own discretion.
>> Looks good, please install when you get your commit access,
> Committed as revno: 111793 and 111789.1.1.
> Is it normal for the later version to be publicly seen?
I think so.
> I have a feeling that it could have been avoided.
Probably.
> IIRC, Sequence went something like:
> 1. unbind
> 2. commit
> 3. couple of more checkins from others
> 4. commit of pending merge from my side.
I'm pretty sure there are steps missing. Between 3 and 4, there must
have been something like "bzr pull" or "bzr merge" and either the 4 was
really a "bzr push" or there was a "bzr bind" some time before.
The way I do it: my `trunk' branch is bound. When I have a patch to
install, I apply it to trunk somehow, then I "bzr commit" and if it
fails, I first "bzr update" then try again.
Stefan
prev parent reply other threads:[~2013-02-15 23:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 14:34 bug#13708: 24.3.50; icomplete, ido, iswitchb: Replace C-s, C-r with C-. and C-, Jambunathan K
2013-02-13 16:52 ` Dmitry Gutov
2013-02-14 4:54 ` Jambunathan K
2013-02-14 5:12 ` Dmitry Gutov
2013-02-14 5:56 ` Leo Liu
2013-02-14 9:19 ` Juri Linkov
2013-02-14 13:52 ` Stefan Monnier
2013-02-14 13:50 ` Stefan Monnier
2013-02-15 20:09 ` Jambunathan K
2013-02-15 23:40 ` Stefan Monnier [this message]
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=jwvmwv5176h.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=13708@debbugs.gnu.org \
--cc=kjambunathan@gmail.com \
/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.