unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ivan Shmakov <ivan@siamics.net>
To: emacs-devel@gnu.org
Subject: Re: using commit identifiers in bug reports
Date: Fri, 23 Jan 2015 20:45:53 +0000	[thread overview]
Message-ID: <87sif1mdj2.fsf@violet.siamics.net> (raw)
In-Reply-To: <83vbjxs0dv.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 23 Jan 2015 22:33:16 +0200")

>>>>> Eli Zaretskii <eliz@gnu.org> writes:
>>>>> Date: Fri, 23 Jan 2015 19:06:58 +0200  From: Dmitry Gutov
>>>>> On 01/23/2015 06:21 PM, Eli Zaretskii wrote:

 >>>> Or, in my case: “as of last week, Emacs…,” right?

 >>> No, that already might be interpreted as "starting from last week".
 >>> Perhaps even my suggestion above might.  So how about "with the
 >>> current trunk, Emacs does this and that"?

	I still feel it useful to include the commit identifier
	somewhere.  Why, report-emacs-bug already puts the version in
	the subject, and on Git ‘master’, a single version value may
	correspond to vastly different trees.

 >> That might be a British vs American English issue.

 > I don't think so.  AFAIK, Glenn's origins are in the UK, and mine are
 > certainly not in the US.  And yet both of us consider that wording
 > awkward and somewhat confusing.

	One more thing to note is that English Wikipedia consistently
	uses “as of” to mean “at that particular point in time” without
	any implication of the state of affairs being /changed/ at that
	same point.  See [1], for instance.

[1] https://en.wikipedia.org/wiki/Special:WhatLinksHere/Template:As_of

-- 
FSF associate member #7257  http://boycottsystemd.org/  … 3013 B6A0 230E 334A



  reply	other threads:[~2015-01-23 20:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87ppahvcoh.fsf@violet.siamics.net>
     [not found] ` <8wwq4nochs.fsf@fencepost.gnu.org>
     [not found]   ` <87r3uvtxly.fsf@violet.siamics.net>
     [not found]     ` <83h9vr2k2o.fsf@gnu.org>
2015-01-18 18:50       ` using commit identifiers in bug reports Ivan Shmakov
2015-01-18 18:58         ` Eli Zaretskii
2015-01-23 14:52           ` Ivan Shmakov
2015-01-23 16:21             ` Eli Zaretskii
2015-01-23 17:06               ` Dmitry Gutov
2015-01-23 20:33                 ` Eli Zaretskii
2015-01-23 20:45                   ` Ivan Shmakov [this message]
2015-01-23 21:23                     ` Eli Zaretskii
2015-01-30 20:54                       ` Ivan Shmakov
2015-01-18 20:33         ` Dmitry Gutov
2015-01-19  3:30           ` Eli Zaretskii
2015-01-19  3:32             ` Dmitry Gutov

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=87sif1mdj2.fsf@violet.siamics.net \
    --to=ivan@siamics.net \
    --cc=emacs-devel@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 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).