similar to: Git autocrlf for Windows - why does the Getting Started guide say to use false?

Right, my understanding is that files that specifically need CRLF should say so via .gitattributes somewhere. autocrlf=false ought to work if your Windows editor doesn’t (or can be persuaded not to) introduce CRLFs. I’ve observed that the Visual Studio editor will detect the line-ending style of the file you’re editing, and imitate it. This works great until you create a new file. 😝 So I’ve

I've been using the mono-repo [ http://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo] and this morning I ran into an issue where I am unable to submit using the mono repo. I traced this down to the fact that many files explicitly have the property svn:eol-style set to native. On the git side, we have core.autocrlf=false, which means that git will checkout

I am ysyncing text files between NT/95/XP machines and Solaris. I noted that the text/ascii files created on the windows platforms contain ^M at the end of each line when transfered to the Solaris system. This can be explained by the binary transmission and can use FTP is ASCII mode to prevent this from happening. It is crutial that we preserve the time stamp, so running dos2unix isn't one

Dear all: I am developing a package in R. While I am running R CMD check, I found the following warning message: Found the following C sources/headers with CRLF line endings: src/hem.c src/random4f.h ISO C requires LF line endings. It seems that it comes from a line ending problem in C. What are CRLF/LF line endings? How can I fix it? Thank you for your help in advance. Best, HJ

I go back and forth between windows and linux, and find myself running into problem with line endings. Is there a way to control the line ending conversion when writing files, such as write and cat? More explicitly I want to be able to write files with LF line endings rather than CRLF line ending on windows; and CRLF line endings instead of LF on linux, and I want to be able to control when the

New to Samba, so excuse me if this is a stupid question, but I've searched the different on line resources and can't find an answer. When I copy Perl scripts from my Windows 2000 machine to the UNIX Samba share on that same machine, a CR/LF appears at the end of each line instead of just the CR, making UNIX unhappy when I go to run those scripts. Any way to have Samba strip the LF

> Just in case it's not clear, the svn for that page is part of the > llvmCore project. Specifically, > > https://llvm.org/svn/llvm-project/llvm/trunk/docs/GettingStarted.html > > Thanks for offering to help with the documentation. Making things > clearer for new users is always a good thing. > > Regards, > Jim If I do a sparse checkout like >svn co

OS=CentOS-5.2 media=Kingston 512Mb usb key Problem: As 'root', when running a script resident on the external drive mounted at /media/disk I receive the following error: /bin/sh: bad interpreter: Permission denied The meduia is a 512Mb USB key formatted as ext2/3 # ll -rwx------ 1 root root 28 Jul 2 17:30 hello.sh # cat hello.sh #!/bin/sh echo Hello World! # which sh /bin/sh I

Hi, I am using Samba 1.9.18. The server is running on Solaris 2.5.1 and the client is on Win NT 4.0 I am annoyed by the Control-M characters appearing in text files when the files are edited on Windows editors and viewed in vi on Sun machine. I had to manually remove the Control-M characters. Is there a way to eliminate the Control M characters ? Thanks Krishna

This patch file adds a missing parameter to the sample source so the dialog sample will work. Also attached is a patch to add an additional optional parameter to wxStaticLine.h. I was going through header files to confirm the other problem and discovered there''s another optional parameter. Roy _______________________________________________ wxruby-users mailing list

I know this process is well documented here http://llvm.org/docs/GettingStarted.html But man do I love scripting things: LLVM Getting Started (See http://llvm.org/docs/GettingStarted.html) ./getttingStarted.sh [-clang] [-compiler-rt] [-test-suite] [-branch branch] [-dir path] [-r rev] By default this script checks out ToT LLVM to the current working directory Project Options: -clang

On Thu, Nov 29, 2012 at 9:41 AM, Joe Abbey <jabbey at arxan.com> wrote: > I know this process is well documented here > http://llvm.org/docs/GettingStarted.html > > But man do I love scripting things: > > LLVM Getting Started (See http://llvm.org/docs/GettingStarted.html) > ./getttingStarted.sh [-clang] [-compiler-rt] [-test-suite] [-branch branch] > [-dir path] [-r

Hi LLVM Devs, I recently finished working for Intel/Movidius, and thought that before I start working on some new LLVM project, that this would be a good time to discard all of my old practices (which began with v2.7, and has gathered crud over the years) and restart with a brand new fresh LLVM approach directly from head. In preparation for doing this, I would like to know what is the

R-devel has been warning for some time about hidden files (in the Unix sense, starting with a period) in source packages. We could get R CMD build and the CRAN incoming scripts to remove these *if* we knew that they were never needed. It seems clear that .Rapp.history .Rhistory .Rbuildindex.xxxxx inst/doc/.build.timestamp are R leftovers, ._.DS_store is from an Apple filesystem and .tex

Is there any option that will covert a text file from one system to the other? I have a few files on linux with extension TXT. There are plain text files. On NT, TXT is associated with the "notepad" and opens with the file as one long string. This is the typical CR/LF conversions between Unix and DOS. Can Samba convert the text files based on the client? Subba Rao subb3@attglobal.net

We have this working. however Some developers edit files using "windows editors" and when they then copy them to the Windows Drive Letter which is mapped to a Unix machine, the resultant file is full of ^M characters..... build breaks..... and so on Until now we have been telling users to run "dos2unix" beforehand, but somebody told me that "Samba" can

Hi Joe, thanks for working on this. My honest opinion on it is that time would be better spent improving the documentation, as the current documentation is archaic. I think this has come up on the list before, but to rehash: * Start out by saying "LLVM can be built with make or CMake, and checked out with svn or git", and have "make", "CMake", "svn", and

I have been reviewing Louis' script (4-setup-sernet-samba4-MEMBER-wheezy.sh) and within the following line (310) is an odd character combination. if [ ${SMBPRINTING} = no ]; then echo "==========Disable Printing ===============================" sed -i '49a\n # disable printing completelyn load printers = non printing = bsdn printcap name = /dev/nulln disable spoolss =

Hi All, I used to always do a minimal install with v4.4, and wget (and other tools) was included. With v5 if i untick *everything* in the installation (incl "base") so that i can install from 1 cd, wget is not included. I couldn't make sense of any of the xml or xml.gz files on the installation cd. (/dev/cdrom/repodata/*), although they do mention wget as 'default'

[This email is either empty or too large to be displayed at this time]