From: Linus Torvalds <torvalds@osdl.org>
To: Christopher Faylor <me@cgf.cx>
Cc: git@vger.kernel.org
Subject: Re: cygwin-latest: compile errors related to sockaddr_storage, dirent->d_type and dirent->d_ino
Date: Thu, 19 Jan 2006 13:16:17 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0601191309130.3240@g5.osdl.org> (raw)
In-Reply-To: <20060119203428.GA5090@trixie.casa.cgf.cx>
On Thu, 19 Jan 2006, Christopher Faylor wrote:
>
> Btw, we're looking to roll out a new release of cygwin which fixes the
> embarrassing typo in sockaddr_storage. It is fixed in cygwin snapshots:
>
> http://cygwin.com/snapshots/
Quick question for cygwin people (I asked this at an earlier point, but I
don't think there was any reply): would cygwin prefer using "vfork()" over
"fork()", or is there no advantage? With vfork(), I could imagine that you
might avoid a lot of strange VM games..
I think almost all of the git fork usage is of the type where "vfork()"
would work fine (git-daemon in non-inetd form is an exception, perhaps the
only one).
So if using vfork() is preferable, we probably should do that. It tends to
be a small performance improvement on Linux too, although on Linux it's
really pretty much in the noise.
Alternatively, is there anything else we can do that makes things easier?
Linus
next prev parent reply other threads:[~2006-01-19 21:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 13:47 cygwin-latest: compile errors related to sockaddr_storage, dirent->d_type and dirent->d_ino Alex Riesen
2006-01-19 5:29 ` Christopher Faylor
2006-01-19 8:59 ` Junio C Hamano
2006-01-19 16:10 ` Christopher Faylor
2006-01-19 20:34 ` Christopher Faylor
2006-01-19 21:16 ` Linus Torvalds [this message]
2006-01-19 21:28 ` Christopher Faylor
2006-01-19 21:44 ` Linus Torvalds
2006-01-19 21:51 ` Christopher Faylor
2006-01-20 1:13 ` [PATCH] fsck-objects: support platforms without d_ino in struct dirent Junio C Hamano
2006-01-20 3:38 ` Christopher Faylor
2006-01-19 10:42 ` cygwin-latest: compile errors related to sockaddr_storage, dirent->d_type and dirent->d_ino Alex Riesen
2006-01-19 18:31 ` Christopher Faylor
2006-01-19 22:08 ` Alex Riesen
2006-01-19 22:51 ` Christopher Faylor
2006-01-19 12:51 ` Petr Baudis
2006-01-19 15:04 ` Alex Riesen
2006-01-19 13:00 ` Petr Baudis
2006-01-19 15:07 ` Alex Riesen
2006-01-20 1:13 ` Junio C Hamano
2006-01-20 13:23 ` Alex Riesen
2006-01-20 1:13 ` [PATCH] DT_UNKNOWN: do not fully trust existence of DT_UNKNOWN Junio C Hamano
2006-01-20 15:01 ` Alex Riesen
2006-01-20 19:10 ` Junio C Hamano
2006-01-20 21:53 ` Alex Riesen
2006-01-21 8:09 ` Junio C Hamano
2006-01-23 13:07 ` Alex Riesen
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=Pine.LNX.4.64.0601191309130.3240@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=me@cgf.cx \
/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).