From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 17970@debbugs.gnu.org
Subject: bug#17970: log-edit creates unwanted ChangeLog buffers
Date: Wed, 09 Jul 2014 11:41:35 -0400 [thread overview]
Message-ID: <16r41uh74g.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83d2ded4c3.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 09 Jul 2014 16:55:24 +0300")
Eli Zaretskii wrote:
>> Perhaps log-edit-changelog-entries should not bother visiting
>> non-existent files.
>
> That wouldn't be TRT when starting a new repository, or a new
> directory in an existing one.
What benefit is there to vc-next-action creating empty ChangeLog buffers
in such cases?
> In addition, if the ignore file mentions ChangeLog, the command could
> deduce automatically what is TRT.
(Then we need an ignore-file parser.)
Why would you have an unversioned ChangeLog, and why would this matter
to vc-next-action?
next prev parent reply other threads:[~2014-07-09 15:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 2:35 bug#17970: log-edit creates unwanted ChangeLog buffers Glenn Morris
2014-07-09 7:09 ` Glenn Morris
2014-07-09 13:55 ` Eli Zaretskii
2014-07-09 15:41 ` Glenn Morris [this message]
2014-07-09 16:28 ` Eli Zaretskii
2014-07-09 16:39 ` Glenn Morris
2014-07-09 16:54 ` Eli Zaretskii
2014-07-09 20:17 ` Glenn Morris
2014-07-10 3:09 ` Stefan Monnier
2014-07-10 14:59 ` Eli Zaretskii
2014-07-10 16:45 ` Stefan Monnier
2014-07-10 16:54 ` Glenn Morris
2014-07-10 17:18 ` Stefan Monnier
2014-07-10 17:22 ` Eli Zaretskii
2014-07-10 17:46 ` Glenn Morris
2014-07-10 18:19 ` Stefan Monnier
2014-07-09 18:54 ` Stefan Monnier
2014-07-09 20:19 ` Glenn Morris
2014-07-09 22:22 ` Stefan Monnier
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=16r41uh74g.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=17970@debbugs.gnu.org \
--cc=eliz@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).