All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Wakeling <joseph.wakeling@webdrake.net>
To: Joseph Wakeling <joseph.wakeling@webdrake.net>, git@vger.kernel.org
Subject: Re: Newbie experience with push over ssh
Date: Wed, 14 Feb 2007 18:00:55 +0000	[thread overview]
Message-ID: <45D34E57.5050004@webdrake.net> (raw)
In-Reply-To: <20070214175219.GA7082@moooo.ath.cx>

Matthias Lederhofer wrote:
> Joseph Wakeling <joseph.wakeling@webdrake.net> wrote:
>> I remember coming across the same issue as Matthieu and never got round
>> to solving it.  In my case the desire is to upload the code onto a
>> remote machine---in particular a cluster where I run simulations.  I
>> don't particularly need that remote code to be in a repo or otherwise,
>> since it's only there to be run, not edited.
> 
> git archive --format=tar HEAD | ssh remote 'cd /some/where;tar xvf -'
> 
> You could put this in a shell script which takes the remote hostname,
> path and optionally the revision to send..

Aaahhh, that looks quite an elegant solution.  Thank you very much!

      reply	other threads:[~2007-02-14 18:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14 14:07 Newbie experience with push over ssh Matthieu Moy
2007-02-14 14:27 ` Matthias Lederhofer
2007-02-14 16:10   ` Joseph Wakeling
2007-02-14 16:25     ` Bill Lear
2007-02-14 16:29       ` Joseph Wakeling
2007-02-14 16:34       ` Bill Lear
2007-02-14 16:48         ` Joseph Wakeling
2007-02-14 16:54           ` Bill Lear
2007-02-14 16:56           ` Matthieu Moy
2007-02-14 17:04             ` Joseph Wakeling
2007-02-14 17:38               ` Nicolas Pitre
2007-02-14 17:47                 ` Joseph Wakeling
2007-02-14 17:51                   ` Jeff King
2007-02-14 18:03                   ` Nicolas Pitre
2007-02-14 16:47       ` Matthieu Moy
2007-02-15 15:35       ` Andreas Ericsson
2007-02-14 17:52     ` Matthias Lederhofer
2007-02-14 18:00       ` Joseph Wakeling [this message]

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

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

  git send-email \
    --in-reply-to=45D34E57.5050004@webdrake.net \
    --to=joseph.wakeling@webdrake.net \
    --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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.