46326 – CRLF in CVS commit message

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 46326 - CRLF in CVS commit message

Summary: CRLF in CVS commit message

Status:	RESOLVED FIXED

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	Team (show other bugs)
Version:	2.1.1
Hardware:	PC Windows XP

Importance:	P3 normal with 1 vote (vote)
Target Milestone:	3.0 M9
Assignee:	Michael Valenta
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2003-11-09 11:19 EST by Luke Usherwood
Modified:	2004-06-18 01:08 EDT (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Luke Usherwood

2003-11-09 11:19:48 EST

Occurs when running Eclipse on Windows, with a CVS repository on Linux.

The commit message gets in CVS gets written to a Linux repository with CRLF
characters, even though the rest of the file is correctly converted to UNIX
style line endings.

This may not be specific to Eclipse.  I did a quick experiment whereby I created
2 text files in Windows. Using cygwin I checked one of them into CVS using the
other one as the log entry.  The file that was being checked-in had it's CRLF
characters correctly changed to LF - however the log message that was inserted
still had CRLF characters.

So either the cvs server is doing something wrong, or perhaps the command-line
cvs and eclipse are both doing the wrong thing.

I'm running CVS version 1.11.6 in Windows/Cygwin, and version 1.11.p1 on Linux
(so it looks like we're long overdue for a Linux upgrade)

Comment 1 Michael Valenta

2003-11-10 09:42:44 EST

*** Bug 45642 has been marked as a duplicate of this bug. ***

Comment 2 Michael Valenta

2004-04-07 11:04:55 EDT

Fix released to HEAD. CRs are now stripped from the comment.

Comment 3 Stephen Coy

2004-06-18 01:08:19 EDT

If this is supposed to be fixed in 3.0RC2, then it has not resolved Bug 45642.