From: Eli Zaretskii <eliz@gnu.org>
To: "Meyer, Thomas" <Thomas.Meyer@dla-marbach.de>
Cc: 58192@debbugs.gnu.org
Subject: bug#58192: 28.2; RCS integration issue
Date: Fri, 30 Sep 2022 13:44:36 +0300 [thread overview]
Message-ID: <83mtahdtuz.fsf@gnu.org> (raw)
In-Reply-To: <4ef14f4b-860f-41df-a785-4c3cca1d5e67@dla-marbach.de> (Thomas.Meyer@dla-marbach.de)
> Date: Fri, 30 Sep 2022 10:01:51 +0200 (CEST)
> From: "Meyer, Thomas" <Thomas.Meyer@dla-marbach.de>
>
> Dear emacs developers, we have an issue with vc-rcs, that we have been
> using for a long time, and which seems to be broken in 28.2 (actually
> first noticed this in 28.1): we are working on the Windows port
> available on http://ftp.gnu.org/gnu/emacs/windows/emacs-28/.
>
> By tracing the activity of e.g. ci command with process monitor, we
> found that the commands fail because an erraneous line break is send
> with the command, e.g.
>
> ----
> PID: 7224, Command line: C:\Windows\system32\cmd.exe /c c:\bin\ci.cmd -j -u1 "-mSummary: bla
> " RCS/x.txt,v
> ----
>
> To reproduce:
>
> find new file in new directory
> C-x v v (vc-next-action)
> Registration will work fine (Registering (c:/Users/meyert/Documents/RCS-test/a.txt)... done)
> change file
> C-x v v (vc-next-action) -> first error: a checkout is done, erasing the changes
> change file again
> C-x v v (vc-next-action) -> second error: check-in fails:
>
> Press C-c C-c when you are done editing.
> Enter a change comment. Type C-c C-c when done
> Checking in c:/Users/meyert/Documents/RCS-test/a.txt...
> progn: Failed (status 1): ci -j -u1 -mSummary: bla
> RCS/a.txt,v
>
> Do you require further details?
Where did the "bla" part come from? Emacs didn't generate it, did it?
It's something you typed at some point, I guess?
More generally, would you please describe the steps in full detail,
including what you typed, exactly?
Also, what does ci.cmd say? I'm not aware of any scripts in the RCS
distribution; 'ci' should be a program, i.e. ci.exe. It could be that
what ci.cmd does has some relevance for this issue.
Thanks.
next prev parent reply other threads:[~2022-09-30 10:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 8:01 bug#58192: 28.2; RCS integration issue Meyer, Thomas
2022-09-30 10:44 ` Eli Zaretskii [this message]
2022-09-30 12:09 ` Eli Zaretskii
[not found] <<4ef14f4b-860f-41df-a785-4c3cca1d5e67@dla-marbach.de>
[not found] ` <<83mtahdtuz.fsf@gnu.org>
[not found] ` <36ba9fa6-e6fd-4d39-8279-785c7ae270b2@dla-marbach.de>
2022-09-30 12:24 ` Eli Zaretskii
[not found] <<<4ef14f4b-860f-41df-a785-4c3cca1d5e67@dla-marbach.de>
[not found] ` <<<83mtahdtuz.fsf@gnu.org>
[not found] ` <<36ba9fa6-e6fd-4d39-8279-785c7ae270b2@dla-marbach.de>
[not found] ` <<83edvtdp95.fsf@gnu.org>
2022-09-30 12:45 ` bug#58192: AW: " Meyer, Thomas
2022-09-30 12:57 ` 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=83mtahdtuz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58192@debbugs.gnu.org \
--cc=Thomas.Meyer@dla-marbach.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 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).