all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@gnu.org>
To: Chris Carlson <cwcarlson@cox.net>
Cc: 9745@debbugs.gnu.org
Subject: bug#9745: 23.3; vc-register does not prompt for initial comment
Date: Thu, 13 Oct 2011 17:15:32 -0400	[thread overview]
Message-ID: <yxqty7ch9u3.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <4E96C9C6.1040302@cox.net> (Chris Carlson's message of "Thu, 13 Oct 2011 04:21:42 -0700")

Chris Carlson <cwcarlson@cox.net> writes:

> This bug report will be sent to the Free Software Foundation,
> not to your local site managers!
> Please write in English if possible, because the Emacs maintainers
> usually do not have translators to read other languages for them.
>
> Your report will be posted to the bug-gnu-emacs@gnu.org mailing list
> and the gnu.emacs.bug news group, and at http://debbugs.gnu.org.
>
> Please describe exactly what actions triggered the bug
> and the precise symptoms of the bug.  If you can, give
> a recipe starting from `emacs -Q':
>
> Performing a vc-register never prompts for an initial comment.  The
> variable vc-initial-comment is defined in vc.el, but it is never
> referenced or used.
>
> Previous versions of Emacs prompted for an initial comment by default,
> but that feature seems to have gotten lost.

Modern VCS do not have an initial message when adding a file (just RCS
did that -- maybe SCCS too), so that feature has been removed. 





  reply	other threads:[~2011-10-13 21:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13 11:21 bug#9745: 23.3; vc-register does not prompt for initial comment Chris Carlson
2011-10-13 21:15 ` Dan Nicolaescu [this message]
2011-10-14  2:39   ` Glenn Morris
2011-10-18  7:00     ` Glenn Morris
2021-09-07 17:46     ` bug#9745: Restore vc-initial-comment functionality for VCS that support it Lars Ingebrigtsen

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=yxqty7ch9u3.fsf@fencepost.gnu.org \
    --to=dann@gnu.org \
    --cc=9745@debbugs.gnu.org \
    --cc=cwcarlson@cox.net \
    /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.