public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jeff King <peff@peff•net>
To: Junio C Hamano <gitster@pobox•com>
Cc: Michael J Gruber <git@drmicha•warpmail.net>,
	"H.Merijn Brand" <h.m.brand@xs4all•nl>,
	git@vger•kernel.org
Subject: Re: Interested in helping open source friends on HP-UX?
Date: Wed, 18 Feb 2015 13:57:34 -0500	[thread overview]
Message-ID: <20150218185734.GB7257@peff.net> (raw)
In-Reply-To: <xmqqpp972h1n.fsf@gitster.dls.corp.google.com>

On Wed, Feb 18, 2015 at 10:47:16AM -0800, Junio C Hamano wrote:

> > It seems like we could use
> >
> >   (cd src && tar cf - .) | (cd dst && tar xf -)
> >
> > here as a more portable alternative. I don't think we can rely on rsync
> > being everywhere.
> 
> Thanks; I wasn't even aware that we used rsync in our tests.  We
> certainly do not want to rely on it.

I don't think we do.

Grepping for rsync in t/, it is mentioned in three places:

  1. In t1509, we use it, but that test script does not run unless you
     set a bunch of environment variables to enable it.

  2. In a sample patch for t4100. Obviously this one doesn't execute. :)

  3. In t5500, to test "rsync:" protocol supported. This is behind a
     check that we can run rsync at all (though it does not properly use
     prereqs or use the normal "skip" procedure).

> Why not "cp -r src dst", though?

I was assuming that the "-P" in the original had some purpose. My "cp
-r" does not seem to dereference symlinks, but maybe there is something
I am missing.

-Peff

  reply	other threads:[~2015-02-18 18:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11  7:46 Interested in helping open source friends on HP-UX? Junio C Hamano
2015-02-18 16:00 ` H.Merijn Brand
2015-02-18 17:46   ` Michael J Gruber
2015-02-18 18:25     ` Jeff King
2015-02-18 18:47       ` Junio C Hamano
2015-02-18 18:57         ` Jeff King [this message]
2015-02-19 10:33           ` Michael J Gruber
2015-02-19 11:14             ` H.Merijn Brand
2015-02-19 11:20               ` Michael J Gruber
2015-02-19 12:54                 ` Jeff King
2015-02-19 13:21                   ` Michael J Gruber
2015-02-19 18:56                     ` H.Merijn Brand
2015-03-03 14:55                       ` Michael J Gruber
2015-03-03 15:30                         ` H.Merijn Brand
2015-03-03 16:05                           ` Michael J Gruber
2015-03-03 22:25                             ` H.Merijn Brand
2015-02-20  1:48                     ` Jeff King
2015-02-20 10:36                       ` Michael J Gruber
2015-02-20 10:49                         ` Jeff King
2015-02-20 11:24                           ` H.Merijn Brand
2015-02-18 19:22         ` H.Merijn Brand
2015-02-18 19:20     ` H.Merijn Brand
2015-02-21 23:31   ` David Aguilar

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=20150218185734.GB7257@peff.net \
    --to=peff@peff$(echo .)net \
    --cc=git@drmicha$(echo .)warpmail.net \
    --cc=git@vger$(echo .)kernel.org \
    --cc=gitster@pobox$(echo .)com \
    --cc=h.m.brand@xs4all$(echo .)nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox