From: Boyd Lynn Gerber <gerberb@zenez.com>
To: Aidan Van Dyk <aidan@highrise.ca>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] Add NO_RSYNC to allow building without rsync
Date: Wed, 30 Jul 2008 15:42:09 -0600 [thread overview]
Message-ID: <alpine.LNX.1.10.0807301539160.13032@xenau.zenez.com> (raw)
In-Reply-To: <20080730204948.GK10399@yugib.highrise.ca>
On Wed, 30 Jul 2008, Aidan Van Dyk wrote:
> * Junio C Hamano <gitster@pobox.com> [080730 16:11]:
> > > I came about this because SCO OpenServer doesnt' have mkdtemp. But I never use
> > > rsync, so making it optional was an easy fix.
> >
> > Perhaps "make NO_MKDTEMP=YesPlease" is a much better fix for your
> > particular environment?
>
> Yes, I found that out after...
>
> > The patch is seriously whitespace damaged, in any case.
>
> Ooops... copy-n-paste from git-format-patch|more on some crappy sco terminal
> through a screen session... I guess someone in there translated tabs to
> spaces...
I do have rsync. I use it all the time on OpenServer 6. I have automated
rsync backups of certain Openserver 6 machines.
tech0 > rsync --version
rsync version 3.0.2 protocol version 30
Copyright (C) 1996-2008 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints,
socketpairs, hardlinks, symlinks, no IPv6, batchfiles, inplace,
append, ACLs, no xattrs, iconv, no symtimes
tech0.zenez.com and osr600.zenez.com are OpenServer 6 machines.
--
Boyd Gerber <gerberb@zenez.com>
ZENEZ 1042 East Fort Union #135, Midvale Utah 84047
prev parent reply other threads:[~2008-07-30 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 18:52 [PATCH] Add NO_RSYNC to allow building without rsync Aidan Van Dyk
2008-07-30 19:33 ` Linus Torvalds
2008-07-30 19:49 ` Aidan Van Dyk
2008-07-30 20:11 ` Junio C Hamano
2008-07-30 20:49 ` Aidan Van Dyk
2008-07-30 21:42 ` Boyd Lynn Gerber [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=alpine.LNX.1.10.0807301539160.13032@xenau.zenez.com \
--to=gerberb@zenez.com \
--cc=aidan@highrise.ca \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 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 NNTP newsgroup(s).