From: Alan Mackenzie <acm@muc.de>
To: Jim Porter <jporterbugs@gmail.com>
Cc: emacs-devel@gnu.org, Robert Pluim <rpluim@gmail.com>
Subject: Re: git commit message checker won't let me commit a new file.
Date: Wed, 19 Jul 2023 11:10:32 +0000 [thread overview]
Message-ID: <ZLfEqHOjMn_VOBOk@ACM> (raw)
In-Reply-To: <829deea6-a17c-47ba-104d-37a88d081a3e@gmail.com>
Hello, Jim.
On Tue, Jul 18, 2023 at 15:05:34 -0700, Jim Porter wrote:
> On 7/18/2023 1:23 PM, Alan Mackenzie wrote:
> > Hello, Emacs.
> > I'm trying to commit a fix for bug #64642. This involves adding a new
> > test file.
> > The commit message checker says "File
> > test/src/comp-resources/comp-test-funcs-dyn2.el: cannot be read: [No
> > such file or directory]
> > Commit aborted; please see the file CONTRIBUTE"
> That's surprising. This works perfectly for me. Can you describe in more
> detail how you're committing your change? Here's what I did:
> $ git checkout -b testing
> $ echo hi > test/src/comp-resources/comp-test-funcs-dyn2.el
> $ git add test/src/comp-resources/comp-test-funcs-dyn2.el
> $ git commit
> In my editor, I add this for the commit message:
> * test/src/comp-resources/comp-test-funcs-dyn2.el: New file.
> The commit hooks run successfully for me and don't produce any errors.
> Based on the output you see, I'm guessing the issue is in the
> `commit-msg` hook, but I don't see anything in there that would do this.
The fault is mine. I still had remnants of my own experiments with
commit-msg in a version of commit-msg, and I had lots of symbolic links
from my various repositories pointing at this. So I can sort it out,
now.
Sorry for wasting your time.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2023-07-19 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 20:23 git commit message checker won't let me commit a new file Alan Mackenzie
2023-07-18 22:05 ` Jim Porter
2023-07-19 9:22 ` Alan Mackenzie
2023-07-19 9:34 ` Robert Pluim
2023-07-19 11:10 ` Alan Mackenzie [this message]
2023-07-19 11:48 ` 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=ZLfEqHOjMn_VOBOk@ACM \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=jporterbugs@gmail.com \
--cc=rpluim@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).