git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Roberto Garcia'" <eltitorober1985@gmail.com>, <git@vger.kernel.org>
Subject: RE: Clone repository computer A to remote B doenst work
Date: Sat, 25 Nov 2017 10:52:30 -0500	[thread overview]
Message-ID: <003d01d36605$69bfe650$3d3fb2f0$@nexbridge.com> (raw)
In-Reply-To: <CAOeKBwpUDD_C5mQ54Aa2pj72aVkp9F2rkmGrSVMC81d6gJQRew@mail.gmail.com>

On November 25, 2017 4:31 AM Roberto Garcia wrote:

>I'm trying clone in windows a git repository to other remote machine (NAS Linux based).
>I have installed git for windows but i didn't installed nothing in the other remote machine (NAS Linux based).

You have two choices:
1. Install git on your LINYX machine, which you probably can't do if it's a pure NAS outside of your control.
2. Run everything off Windows as git in local mode. Mount the NAS as a windows drive. In a command terminal:
	a. cd X:\Share\repo.git #you'll have to mkdir this
	b. git init --bare #creates a new empty repo on your NAS
	c. cd C:\MyStuff #where you keep your clones
	d. git clone -l X:\Share\repo.git #clone the bare repository
	e. Start adding stuff (git add, git commit)
	f. git push   # to move commits to your NAS repo.

Then you have your relationship and can push/pull from your NAS entirely from within Windows executing objects. Change directories and drive letters accordingly. -l means local, so git won't be starting any git-upload-pack processes remotely. Variations on this should work.

Good luck.

Randall


  reply	other threads:[~2017-11-25 15:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-25  9:31 Clone repository computer A to remote B doenst work Roberto Garcia
2017-11-25 15:52 ` Randall S. Becker [this message]
2017-11-25 22:38 ` Johannes Schindelin
2017-11-26  8:38   ` Roberto Garcia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='003d01d36605$69bfe650$3d3fb2f0$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=eltitorober1985@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).