unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: esr@thyrsus.com (Eric S. Raymond)
Cc: emacs-devel@gnu.org
Subject: Re: Everyone, please stop making my life more difficult
Date: Fri, 12 Sep 2014 09:08:45 +0300	[thread overview]
Message-ID: <834mwd8j6a.fsf@gnu.org> (raw)
In-Reply-To: <20140912043652.4D6D8380604@snark.thyrsus.com>

> From: esr@thyrsus.com (Eric S. Raymond)
> Date: Fri, 12 Sep 2014 00:36:52 -0400 (EDT)
> 
> While running my latest repository conversion, I found this comment
> 
>     revno: 116811.1.662
>     fixes bug: http://debbugs.gnu.org/18384
>     committer: Eli Zaretskii <eliz@gnu.org>
>     branch nick: emacs-24
>     timestamp: Tue 2014-09-02 18:16:42 +0300
>     message:
>       Fix bug #18384 with incorrect reporting of row number by posn-col-row.
>       
>        lisp/subr.el (posn-col-row): Revert the change from commit
>        r99634.2.576 eliz@gnu.org-20101113210758-8ml5kibjtza5ysmb, which
>        was inadvertently merged from emacs-23 release branch in r102428
>        monnier@iro.umontreal.ca-20101118035414-yvlg7k7dk4k4l3q, and
>        introduced an off-by-one error in the reported row when there is a
>        header line.
>       
>        src/dispnew.c (buffer_posn_from_coords): Fix an off-by-one error in
>        the reported row in the case of a window with a header line, by
>        improving on the fix committed in r106022
>        eliz@gnu.org-20111008105850-ht4tvsayohvr1kjc.
> 
> There are two things about this comment that make my life
> unnecessarily more difficult.
> 
> 1) People are continuing to embed bzr revision numbers like
>    r99634.2.576 and r102428 in comments.  Do not do this.  

There's no easy way to refer to an old commit in an unequivocal way.

>    They're soon going to cease being meaningful, and every time
>    I have to run another conversion to clean these out it costs
>    me eight to ten hours.

I thought you already have machinery in place to do that
automatically.

> 2) "eliz@gnu.org-20101113210758-8ml5kibjtza5ysmb" Um.  What the *hell*?

It's a bzr revision-id.  You can use it in "bzr log" or any other bzr
command that accepts a revision spec.

>    This is not the time to be inventing some random new magic-cookie
>    commit reference format that my tools don't know how to recognize.
>    That should have been 2010-11-13T21:07:58Z!eliz@gnu.org (I think).

I was certain you already deal with this.  If not, please tell what
information you need to convert this automatically.

> The correct format for a commit reference that will remain
> intelligible across every VCS, forever, is this:
> 
> <RFC3339-date>!<email-address>
> 
> Example: 2010-11-13T21:07:58Z!eliz@gnu.org

How can I produce this automatically given the information I have
about the revision, i.e. its number and, possibly, revision-id?
Is it possible to write a command to do this?



  reply	other threads:[~2014-09-12  6:08 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-12  4:36 Everyone, please stop making my life more difficult Eric S. Raymond
2014-09-12  6:08 ` Eli Zaretskii [this message]
2014-09-12  9:55   ` Eric S. Raymond
2014-09-12 10:33     ` Eli Zaretskii
2014-09-12 10:49       ` Gregor Zattler
2014-09-12 13:05         ` Eli Zaretskii
2014-09-12 13:19           ` David Kastrup
2014-09-12 13:29             ` Eli Zaretskii
2014-09-12 13:55               ` Andreas Schwab
2014-09-12 14:12                 ` Eli Zaretskii
2014-09-12 15:17                 ` Eli Zaretskii
2014-09-12 15:21                   ` Andreas Schwab
2014-09-12 17:15                     ` Eli Zaretskii
2014-09-12 17:43                       ` Andreas Schwab
2014-09-12 15:53                   ` David Kastrup
2014-09-12 17:22                     ` Eli Zaretskii
2014-09-12 19:28                       ` David Kastrup
2014-09-12 19:59                         ` Eli Zaretskii
2014-09-12 13:57               ` David Kastrup
2014-09-12 14:26                 ` Eli Zaretskii
2014-09-12 11:38       ` Eric S. Raymond
2014-09-12 13:14         ` Eli Zaretskii
2014-09-12 16:27           ` Eric S. Raymond
2014-09-12 11:46       ` Harald Hanche-Olsen
2014-09-12 13:56         ` Paul Eggert
2014-09-12 15:08     ` Barry Warsaw
2014-09-12 16:16       ` Eric S. Raymond
2014-09-12  6:47 ` Thien-Thi Nguyen
2014-09-12  7:25   ` David Kastrup
2014-09-12  9:34     ` Thien-Thi Nguyen
2014-09-12  8:18 ` Eli Zaretskii
2014-09-12  8:34   ` Eric S. Raymond
2014-09-12  8:40     ` Eric S. Raymond
2014-09-12 11:47     ` Andreas Schwab
2014-09-12 11:57       ` Eric S. Raymond
2014-09-12 12:17         ` David Kastrup
2014-09-12 13:51         ` Andreas Schwab
2014-09-12 15:54           ` Eric S. Raymond
2014-09-12 16:04             ` David Kastrup
2014-09-12 16:18             ` Andreas Schwab
2014-09-12 16:28               ` Eric S. Raymond
2014-09-12 16:43                 ` David Kastrup
2014-09-12 20:19             ` resolving ambiguity in action stamps (was: Everyone, please stop making my life more difficult) Joshua Judson Rosen
2014-09-12 20:41               ` Eric S. Raymond
2014-09-12 21:44                 ` resolving ambiguity in action stamps Joshua Judson Rosen
2014-09-13  3:45                 ` resolving ambiguity in action stamps (was: Everyone, please stop making my life more difficult) Stephen J. Turnbull
2014-09-13  5:35                   ` Eric S. Raymond
2014-09-13  6:57                     ` Stephen J. Turnbull
2014-09-13  7:26                       ` resolving ambiguity in action stamps Harald Hanche-Olsen
2014-09-13 10:50                         ` Eric S. Raymond
2014-09-13 12:43                           ` Yuri Khan
2014-09-14  7:34                           ` Stephen J. Turnbull
2014-09-14 10:55                             ` Eric S. Raymond
2014-09-14 11:03                               ` David Kastrup
2014-09-14 13:30                               ` Stephen J. Turnbull
2014-09-14 14:06                                 ` David Kastrup
2014-09-14 15:51                                   ` Stephen J. Turnbull
2014-09-14 14:21                                 ` Eric S. Raymond
2014-09-14 15:45                                   ` Stephen J. Turnbull
2014-09-14 15:59                                     ` David Kastrup
2014-09-14 17:12                                     ` Eric S. Raymond
2014-09-15  0:09                                       ` Stephen J. Turnbull
2014-09-13  8:51                       ` Andreas Schwab
2014-09-12 14:12       ` Everyone, please stop making my life more difficult Sam Steingold
2014-09-12 14:36         ` David Kastrup
2014-09-12 14:44           ` Yuri Khan
2014-09-12 15:24             ` Sam Steingold
2014-09-12 15:59               ` David Kastrup
2014-09-12 16:12             ` Eric S. Raymond
2014-09-12 17:06               ` Stefan Monnier
2014-09-12 20:35                 ` Thien-Thi Nguyen
2014-09-12 15:21           ` Sam Steingold
2014-09-12 15:34             ` Harald Hanche-Olsen
2014-09-12 15:51             ` David Kastrup
2014-09-12 17:44             ` Stephen J. Turnbull
2014-09-12 17:58               ` David Caldwell
2014-09-12 19:19                 ` Stephen J. Turnbull
2014-09-12 18:01               ` Harald Hanche-Olsen
2014-09-12 19:36             ` Joshua Judson Rosen
2014-10-28 21:11               ` Randal L. Schwartz
2014-09-12 15:30         ` Phillip Lord
2014-09-12 15:57           ` David Kastrup
2014-09-12 17:10           ` 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

  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=834mwd8j6a.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=esr@thyrsus.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).