From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: kfogel@red-bean.com, cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: bug#881: patch for bug #881
Date: Thu, 07 Jan 2010 06:14:46 +0200 [thread overview]
Message-ID: <83y6kablft.fsf@gnu.org> (raw)
In-Reply-To: <f7ccd24b1001061243i3730926bp1950d75988122393@mail.gmail.com>
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Wed, 6 Jan 2010 21:43:44 +0100
> Cc: kfogel@red-bean.com, cyd@stupidchicken.com, emacs-devel@gnu.org
>
> On Wed, Jan 6, 2010 at 19:15, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Type
> >
> > bzr log -r "revid:eliz@gnu.org-20100102213336-hnnaav0wq0al1gni"
> >
> > and see there what syntax I used.
> >
> > It's the same syntax as in "bzr whoami", I simply submitted the string
> > you see in the log of the above revision, enclosed in quotes.
>
> The syntax was clear
Sorry for my misunderstanding.
> I was asking about semantics. I see that a bzr log and qlog show the
> author and not the committer; surely that's all?
For me, it shows both the author and the committer:
revno: 99248
revision-id: eliz@gnu.org-20100102213336-hnnaav0wq0al1gni
parent: eliz@gnu.org-20100102203141-u7k63n409g6mylfm
author: Kevin Ryde <user42@zip.com.au>
committer: Eli Zaretskii <eliz@gnu.org>
branch nick: trunk
timestamp: Sat 2010-01-02 23:33:36 +0200
message:
eieio.texi (Naming Conventions): Correction to xref on elisp
coding conventions, is "Tips" node not "Standards".
next prev parent reply other threads:[~2010-01-07 4:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wrzwp5gd.fsf@stupidchicken.com>
2010-01-06 0:43 ` bug#881: patch for bug #881 Juanma Barranquero
2010-01-06 3:35 ` Karl Fogel
2010-01-06 4:12 ` Juanma Barranquero
2010-01-06 4:19 ` Karl Fogel
2010-01-06 10:12 ` Juanma Barranquero
2010-01-06 18:15 ` Eli Zaretskii
2010-01-06 20:43 ` Juanma Barranquero
2010-01-07 4:14 ` Eli Zaretskii [this message]
2010-01-07 9:13 ` Juanma Barranquero
2010-01-06 4:13 ` Eli Zaretskii
2010-01-06 4:34 ` Stefan Monnier
2010-01-06 7:00 ` Dan Nicolaescu
2010-01-06 7:22 ` Óscar Fuentes
2010-01-06 9:34 ` Stephen J. Turnbull
2010-01-06 14:20 ` Stefan Monnier
2010-01-06 18:29 ` Dan Nicolaescu
2010-01-06 20:19 ` Stefan Monnier
2010-01-07 17:09 ` Dan Nicolaescu
2010-01-07 20:07 ` Stefan Monnier
2010-01-06 18:29 ` Eli Zaretskii
2010-01-06 18:52 ` Óscar Fuentes
2010-01-06 20:20 ` Stefan Monnier
2010-01-06 20:40 ` Eli Zaretskii
2010-01-07 15:33 ` Juanma Barranquero
2010-01-07 17:15 ` bzr --fixes [was Re: bug#881: patch for bug #881] Glenn Morris
2010-01-07 20:12 ` Juanma Barranquero
2010-01-07 20:34 ` bzr --fixes Glenn Morris
2010-01-07 22:35 ` Juanma Barranquero
2010-01-08 9:01 ` Eli Zaretskii
2010-01-08 8:27 ` Eli Zaretskii
2010-01-06 20:00 ` Committing other people's changes (was: bug#881: patch for bug #881) Reiner Steib
2010-01-16 21:50 ` bug#881: patch for bug #881 Chong Yidong
2010-01-16 21:52 ` Juanma Barranquero
2010-01-16 22:30 ` Chong Yidong
2010-01-17 9:38 ` Dan Nicolaescu
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=83y6kablft.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.com \
--cc=lekktu@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 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).