I have SVN up and running and things are working well, except when editing
shell scripts from windows.
My server is RHEL5-based and I will have clients connecting from linux and
windows. Linux commits work great, and even some times from windows.
However some times I commit a file from Windows(r
On 2/23/2011 8:19 AM, Christopher D Haakinson wrote:
I have SVN up and running and things are working well, except when
editing shell scripts from windows.
My server is RHEL5-based and I will have clients connecting from linux
and windows. Linux commits work great, and even some times from
On 2/23/2011 10:19 AM, Christopher D Haakinson wrote:
I have SVN up and running and things are working well, except when
editing shell scripts from windows.
My server is RHEL5-based and I will have clients connecting from linux
and windows. Linux commits work great, and even some times from wind
On Wed, Feb 23, 2011 at 11:39 AM, Les Mikesell wrote:
> On 2/23/2011 10:19 AM, Christopher D Haakinson wrote:
>>
>> I have SVN up and running and things are working well, except when
>> editing shell scripts from windows.
>>
>> My server is RHEL5-based and I will have clients connecting from linux
On 2/23/2011 4:44 PM, Nico Kadel-Garcia wrote:
On Wed, Feb 23, 2011 at 11:39 AM, Les Mikesell wrote:
On 2/23/2011 10:19 AM, Christopher D Haakinson wrote:
I have SVN up and running and things are working well, except when
editing shell scripts from windows.
My server is RHEL5-based and I will
As others have mentioned, you need to set svn:eol-style on files that
MUST have particular line endings. For example, shell scripts and
Makefiles MUST have Unix line endings. DOS Batch files MUST have
Windows line endings.
You might need to check everything out, clean it up, and set the
property o
On Wed, Feb 23, 2011 at 8:48 PM, David Chapman wrote:
> On 2/23/2011 4:44 PM, Nico Kadel-Garcia wrote:
>>
>> On Wed, Feb 23, 2011 at 11:39 AM, Les Mikesell
>>> Short version: set the svn:eol-style property to native on the files
>>> where
>>> you want subversion to manage line endings. Your clie
On Feb 23, 2011, at 19:48, David Chapman wrote:
> On 2/23/2011 4:44 PM, Nico Kadel-Garcia wrote:
>> On Wed, Feb 23, 2011 at 11:39 AM, Les Mikesell wrote:
>>> Short version: set the svn:eol-style property to native on the files where
>>> you want subversion to manage line endings. Your client may h
On 2/23/11 8:03 PM, Nico Kadel-Garcia wrote:
Uh, no. Use of "svn:eol-style" avoids a world of hurt - programmers do not
have to run a script *every* time they check out a file. Requiring users to
run a script to fix line endings in every sandbox is a recipe for disaster.
"dos2unix" and "unix2d
On Wed, 2011-02-23 at 20:03 -0600, Ryan Schmidt wrote:
> On Feb 23, 2011, at 19:48, David Chapman wrote:
> > On 2/23/2011 4:44 PM, Nico Kadel-Garcia wrote:
> >> On Wed, Feb 23, 2011 at 11:39 AM, Les Mikesell wrote:
> >>> Short version: set the svn:eol-style property to native on the files where
> >
-|
|>
| Subject: |
|>
>-------------
On 2/24/2011 8:02 AM, Christopher D Haakinson wrote:
OK, so I've been testing out the svn:eol-style prop and it appears to
work, but it seems like an awful lot of work for such a simple issue.
Is there something server-side I can setup to ensure that all files
contain the correct eol style?
On 2/24/2011 10:02 AM, Christopher D Haakinson wrote:
OK, so I've been testing out the svn:eol-style prop and it appears to
work, but it seems like an awful lot of work for such a simple issue.
Is there something server-side I can setup to ensure that all files
contain the correct eol style?
N
-----------|
|Re: ^M Appends to every line?
|
>--
t;|
|02/24/2011 11:27 AM
|
>|
|>
| Subject: |
|-------->
On 2/24/2011 9:55 AM, Christopher D Haakinson wrote:
I'd like someone to explain how this small shell script, which works
fine, gets corrupted simply by creating a new file and copy/pasting
the text in it. Here's what I'm doing:
1) I have a test shell script that runs fine. Here's the conten
-|
|>
| Subject: |
|>
>--------------
On Feb 24, 2011, at 12:44, Christopher D Haakinson wrote:
> I opened the file in notepad and added a couple blank lines under my exit 0
> and it worked!! How weird is that?
Sounds normal to me. I text file is not a text file, according to UNIX
definitions, if it does not end with a newline.
On Thu, Feb 24, 2011 at 12:55 PM, Christopher D Haakinson <
cdhaa...@us.ibm.com> wrote:
> 2) I copy this entire script from notepad in windows into a new file named
> test2.sh, also in notepad.
>
The guy who wrote "Notepad" and had them put it on Windows as a text editor
should be shot, hung, and
On Fri, Feb 25, 2011 at 12:08, David Weintraub wrote:
> For those who want something a bit more GUI oriented, there's ScitTE
> (http://www.scintilla.org/SciTE.html). And a great Notepad replacement is
> Notepad++ (http://notepad-plus-plus.org/). It provides a very similar
> looking Notepad like i
On 2/24/2011 8:02 AM, Christopher D Haakinson wrote:
OK, so I've been testing out the svn:eol-style prop and it appears to
work, but it seems like an awful lot of work for such a simple issue.
Is there something server-side I can setup to ensure that all files
contain the correct eol style?
As
21 matches
Mail list logo
