unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: [Emacs] request: better subject lines
Date: Wed, 3 May 2017 12:26:47 +0200	[thread overview]
Message-ID: <20170503102647.GA29662@tuxteam.de> (raw)
In-Reply-To: <8737cmi837.fsf@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, May 03, 2017 at 05:49:00PM +0800, Danny YUE wrote:
> 
> On 2017-05-03 08:49, tomas@tuxteam.de wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Tue, May 02, 2017 at 11:12:05PM +0800, Danny YUE wrote:
> >
> > [...]
> >
> >> Sharp, but makes sense.
> >
> > Sorry if it came across as "sharp". On a second reading I see what
> > you mean. That wasn't my intention.

[...]

> I believe there is a misunderstanding here, and I apologize if my
> expression made this happen.

Nevertheless you made me realize a point I'm glad I realized. So thanks
for that :)

> In fact I wanted to say "I agree with you". Maybe I should have put this
> line in front of my last email ;)
> 
> I took myself as an example to show that using (and making) better tool
> makes more sense than forcing every other human being to follow one
> pattern that cannot be easily judged better or worse.
> 
> Personally I do not think adding [TAG] into the subject line is a good
> idea, because that is more like a personal preference than something
> which really brings benefits. Some people favor it, some people hate
> it, some others don't really care, more of a taste instead of
> correctness.

I got from your message that *in content* we do agree, yes.

> Sorry again for unclear message.

No need to -- something good came out of that :-)

cheers
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlkJsGcACgkQBcgs9XrR2kYrHwCfZ1RnlBCCBC2qqkMroU+Vc0kL
m6AAnjd4PEGst4Tyzyq/GBoSyvSzhB3Q
=CixP
-----END PGP SIGNATURE-----



  reply	other threads:[~2017-05-03 10:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-30 15:39 [GNU-Emacs] request: better subject lines Carlos Konstanski
2017-04-30 16:38 ` Óscar Fuentes
2017-04-30 17:15 ` allan gottlieb
2017-05-01  3:03 ` Emanuel Berg
2017-05-02 12:52 ` [Emacs] " ken
2017-05-02 13:41   ` tomas
2017-05-02 15:12     ` Danny YUE
2017-05-03  8:49       ` tomas
2017-05-03  9:49         ` Danny YUE
2017-05-03 10:26           ` tomas [this message]
2017-05-02 17:05     ` ken
2017-05-02 17:32       ` hector
2017-05-02 18:38       ` Bob Proulx
2017-05-03  8:56         ` tomas
2017-05-02 14:34   ` Harry Putnam
2017-05-02 19:04     ` Emanuel Berg
2017-05-02 20:43 ` [GNU-Emacs] " Bob Proulx
2017-05-03  0:57   ` Emanuel Berg
2017-05-03  5:10     ` Bob Proulx
2017-05-03 12:38       ` Óscar Fuentes
2017-05-03 20:12       ` Emanuel Berg
2017-05-03 23:25         ` Nick Dokos
2017-05-04  1:34           ` Emanuel Berg
2017-05-04 17:02             ` Nick Dokos
2017-05-04 18:29               ` Emanuel Berg
2017-05-04  5:26         ` Marcin Borkowski
2017-05-04  6:55           ` Emanuel Berg
2017-05-04  6:59           ` Emanuel Berg
2017-05-04  2:01       ` Emanuel Berg
2017-05-03  2:34   ` allan gottlieb
2017-05-04 15:40     ` Emanuel Berg

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=20170503102647.GA29662@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=help-gnu-emacs@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.
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).