all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Reiner Steib <reiner.steib@gmx.de>
Cc: 8057@debbugs.gnu.org
Subject: bug#8057: 23.2.93; (PCL-CVS and) log-edit
Date: Fri, 11 Oct 2019 22:31:32 +0200	[thread overview]
Message-ID: <87sgnzkorf.fsf@gnus.org> (raw)
In-Reply-To: <20110216172108.exdjr8vyocgsw0sk@imap.uni-ulm.de> (Reiner Steib's message of "Wed, 16 Feb 2011 17:21:08 +0100")

Reiner Steib <reiner.steib@gmx.de> writes:

> assume you have this new entry in the file/buffer ChangeLog:
>
> | 2011-02-16  Reiner Steib  <foo@invalid>
> |
> | 	* some-longish-file-name.txt (module): New.
>
> In the *cvs* buffer, you mark the files some-longish-file-name.txt and
> ChangeLog, then hit `C' (cvs-mode-commit-setup).
>
> In Emacs 23.2.93, I get this log-edit buffer:
>
> | Summary:
> |
> | * some-longish-file-name.txt (module): New.
>
> Problem (1):
>
> The user has no information what will happen to the pseudo headers
> (e.g. "Summary:") and the empty lines.

This was eight years ago, and I think that in practice the introduction
of these header lines didn't lead to much confusion, so I think adding a
help text (as suggested by this bug report) is unnecessary, and I'm
closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      parent reply	other threads:[~2019-10-11 20:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-16 16:21 bug#8057: 23.2.93; (PCL-CVS and) log-edit Reiner Steib
2011-02-17  0:25 ` Glenn Morris
2011-02-17  7:27   ` Glenn Morris
2011-07-14 18:41 ` Lars Magne Ingebrigtsen
2011-09-11  3:54 ` Lars Magne Ingebrigtsen
2011-09-11  5:02   ` Stefan Monnier
2019-10-11 20:31 ` Lars Ingebrigtsen [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sgnzkorf.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=8057@debbugs.gnu.org \
    --cc=reiner.steib@gmx.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.