# Common setting for interoperability repo across windows and unix? 7 messages from 2009-11-03 to 2009-11-04. Participants: Dilip M, Avery Pennarun, Vietor Liu, Anthony W. Youngman, Shawn O. Pearce, Erik Faye-Lund. Thread: https://gitlist.dev/t/21462 ## Dilip M, 2009-11-03 15:09 Subject: Common setting for interoperability repo across windows and unix? Message-ID: URL: https://gitlist.dev/e/c94f8e120911030709h29c5b8edr53df269632990e81%40mail.gmail.com ``` Hello, I have repo in unix. The same repo is cloned onto windows.I have set "core.autocrlf=input" in both the repos. When I do some change to a file in windows and push to unix repo, I get file deleted If I do "git status"? What is the setting to be done if I want an repo to be access/push/pulled across windows and unix? -- Dilip ``` ## Avery Pennarun, 2009-11-03 15:33 Subject: Re: Common setting for interoperability repo across windows and unix? Message-ID: <32541b130911030733i734b9f6doc366934873bf7713@mail.gmail.com> URL: https://gitlist.dev/e/32541b130911030733i734b9f6doc366934873bf7713%40mail.gmail.com In-Reply-To: ``` On Tue, Nov 3, 2009 at 11:09 AM, Dilip M wrote: > I have repo in unix. The same repo is cloned onto windows.I have set > "core.autocrlf=input" in both the repos. > > When I do some change to a file in windows and push to unix repo, I > get file deleted If I do "git status"? > > What is the setting to be done if I want an repo to be > access/push/pulled across windows and unix? It sounds like you are pushing to the currently-checked-out branch of a non-bare repo. If this is true, you should do one of the following: - have a central "bare" repo (created with git init --bare) and push/pull from that rather than directly - pull, rather than push, when transferring data between repos. You can pull from a Windows box by running git-daemon on that box from the command line. (It's easier than it sounds.) Have fun, Avery ``` ## Vietor Liu, 2009-11-04 00:46 Subject: Re: Common setting for interoperability repo across windows and unix? Message-ID: <1257295578.2212.4.camel@localhost.localdomain> URL: https://gitlist.dev/e/1257295578.2212.4.camel%40localhost.localdomain In-Reply-To: ``` On Tue, 2009-11-03 at 20:39 +0530, Dilip M wrote: > Hello, > > I have repo in unix. The same repo is cloned onto windows.I have set > "core.autocrlf=input" in both the repos. > > When I do some change to a file in windows and push to unix repo, I > get file deleted If I do "git status"? > > What is the setting to be done if I want an repo to be > access/push/pulled across windows and unix? > > > msysgit, test: core.autocrlf=false ``` ## Anthony W. Youngman, 2009-11-04 21:45 Subject: Re: Common setting for interoperability repo across windows and unix? Message-ID: URL: https://gitlist.dev/e/S0ax5AE0Xf8KFwjv%40thewolery.demon.co.uk In-Reply-To: <32541b130911030733i734b9f6doc366934873bf7713@mail.gmail.com> ``` In message <32541b130911030733i734b9f6doc366934873bf7713@mail.gmail.com>, Avery Pennarun writes >You can pull from a Windows box by running git-daemon on that box from >the command line. (It's easier than it sounds.) That presumes you're running Cygwin ... git-daemon doesn't (currently) work on msysgit. Currently I run git-daemon on my linpus netbook and pull/push from windows. Cheers, Wol -- Anthony W. Youngman - anthony@thewolery.demon.co.uk ``` ## Avery Pennarun, 2009-11-04 22:59 Subject: Re: Common setting for interoperability repo across windows and unix? Message-ID: <32541b130911041459y7a2201a3r18601522187891f2@mail.gmail.com> URL: https://gitlist.dev/e/32541b130911041459y7a2201a3r18601522187891f2%40mail.gmail.com In-Reply-To: ``` On Wed, Nov 4, 2009 at 4:45 PM, Anthony W. Youngman wrote: > In message <32541b130911030733i734b9f6doc366934873bf7713@mail.gmail.com>, > Avery Pennarun writes >> You can pull from a Windows box by running git-daemon on that box from >> the command line.  (It's easier than it sounds.) > > That presumes you're running Cygwin ... > > git-daemon doesn't (currently) work on msysgit. Currently I run git-daemon > on my linpus netbook and pull/push from windows. I didn't know that. Windows sockets are mercifully very nearly compatible with Linux ones, so hopefully this wouldn't be too hard to fix for someone that needs it. (Not me; I prefer cygwin over msys in all cases.) Avery ``` ## Shawn O. Pearce, 2009-11-04 23:01 Subject: Re: Common setting for interoperability repo across windows and unix? Message-ID: <20091104230122.GK10505@spearce.org> URL: https://gitlist.dev/e/20091104230122.GK10505%40spearce.org In-Reply-To: <32541b130911041459y7a2201a3r18601522187891f2@mail.gmail.com> ``` Avery Pennarun wrote: > > > > git-daemon doesn't (currently) work on msysgit. Currently I run git-daemon > > on my linpus netbook and pull/push from windows. > > I didn't know that. Windows sockets are mercifully very nearly > compatible with Linux ones, so hopefully this wouldn't be too hard to > fix for someone that needs it. (Not me; I prefer cygwin over msys in > all cases.) git-daemon relies on fork, do work, then later exec. Windows lacks this concept. Making it hard to port. -- Shawn. ``` ## Erik Faye-Lund, 2009-11-04 23:10 Subject: Re: Common setting for interoperability repo across windows and unix? Message-ID: <40aa078e0911041510p645c37c3i238fbf0eb568aba0@mail.gmail.com> URL: https://gitlist.dev/e/40aa078e0911041510p645c37c3i238fbf0eb568aba0%40mail.gmail.com In-Reply-To: <20091104230122.GK10505@spearce.org> ``` On Thu, Nov 5, 2009 at 12:01 AM, Shawn O. Pearce wrote: > Avery Pennarun wrote: >> > >> > git-daemon doesn't (currently) work on msysgit. Currently I run git-daemon >> > on my linpus netbook and pull/push from windows. >> >> I didn't know that.  Windows sockets are mercifully very nearly >> compatible with Linux ones, so hopefully this wouldn't be too hard to >> fix for someone that needs it.  (Not me; I prefer cygwin over msys in >> all cases.) > > git-daemon relies on fork, do work, then later exec.  Windows lacks > this concept.  Making it hard to port. Before anyone starts hacking: I've got a working git-daemon on Windows, based on some old patches from Mike Pape, plus some extending of the start_async-api. It's still not ready for submission, but I think I've got the last important technical details nailed down now, all that is needed is a fair share of clean-up. Hopefully I'll have it ready for submission during the week-end some time. -- Erik "kusma" Faye-Lund ```