Common setting for interoperability repo across windows and unix?

[Dilip M]

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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Avery Pennarun]

On Tue, Nov 3, 2009 at 11:09 AM, Dilip M <[hidden email]> 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Vietor Liu-2]

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




--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Anthony W. Youngman]

In message
<[hidden email]>, Avery
Pennarun <[hidden email]> 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 - [hidden email]

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Avery Pennarun]

On Wed, Nov 4, 2009 at 4:45 PM, Anthony W. Youngman
<[hidden email]> wrote:
> In message <[hidden email]>,
> Avery Pennarun <[hidden email]> 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Shawn O. Pearce]

Avery Pennarun <[hidden email]> 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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Erik Faye-Lund]

On Thu, Nov 5, 2009 at 12:01 AM, Shawn O. Pearce <[hidden email]> wrote:

> Avery Pennarun <[hidden email]> 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html