unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: dptd dptd <dptdescribe@gmail.com>
Cc: 25565@debbugs.gnu.org
Subject: bug#25565: mark-whole-buffer and unnecessary (point) call
Date: Sun, 29 Jan 2017 05:40:59 +0200	[thread overview]
Message-ID: <83mveay1mc.fsf@gnu.org> (raw)
In-Reply-To: <63A9E421-58EB-4E02-9F71-B250ADFB0BCD@gmail.com> (message from dptd dptd on Sat, 28 Jan 2017 23:24:02 +0200)

> From: dptd dptd <dptdescribe@gmail.com>
> Date: Sat, 28 Jan 2017 23:24:02 +0200
> Cc: 25565@debbugs.gnu.org
> 
> It looks really strange to copy-and-paste the same
> explanation for each file / function.

You shouldn't.  The format is this:

  * file (func1, func2, func3): Change description.

If you type "C-x 4 a" inside every function, Emacs will format the
list for you, even if it's longer than a single line.  Then write the
description at the end.

> Btw. why in my patch next to the ID is so strange date? Mon Sep 17
> 00:00:00 2001?

I don't know.  What did you do to produce the patch?





  reply	other threads:[~2017-01-29  3:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-28 15:33 bug#25565: mark-whole-buffer and unnecessary (point) call dptd dptd
2017-01-28 19:08 ` Eli Zaretskii
2017-01-28 21:24   ` dptd dptd
2017-01-29  3:40     ` Eli Zaretskii [this message]
2017-01-29  7:23       ` dptd dptd
2017-01-29 10:41         ` Stephen Berman
2017-01-29 13:27           ` dptd dptd
2017-01-29 19:48             ` Stephen Berman
2017-01-29 20:46               ` dptd dptd
2017-01-29 21:29                 ` Stephen Berman
2017-03-24  6:23                   ` dptd dptd
2017-03-24  7:23                     ` Eli Zaretskii
2017-03-24  7:29                       ` dptd dptd
2017-04-28  8:28                 ` Eli Zaretskii
2017-01-29 15:25         ` Eli Zaretskii

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=83mveay1mc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=25565@debbugs.gnu.org \
    --cc=dptdescribe@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).