From: Linus Torvalds <torvalds@linux-foundation.org>
To: Aidan Van Dyk <aidan@highrise.ca>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add NO_RSYNC to allow building without rsync
Date: Wed, 30 Jul 2008 12:33:17 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0807301231050.3334@nehalem.linux-foundation.org> (raw)
In-Reply-To: <20080730185225.GG10399@yugib.highrise.ca>
On Wed, 30 Jul 2008, Aidan Van Dyk wrote:
>
> I came about this because SCO OpenServer doesnt' have mkdtemp. But I never use
> rsync, so making it optional was an easy fix.
Hmm. Without mkdtemp(), maybe you could just do a trivial compat function
somethin glike
char *git_mkdtemp(char *template)
{
char *n = mktemp(template);
if (mkdir(n))
n = NULL;
return n;
}
instead?
Linus
next prev parent reply other threads:[~2008-07-30 19:37 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 [this message]
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
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.LFD.1.10.0807301231050.3334@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=aidan@highrise.ca \
--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 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).