From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Perl Win32::Shortcut screws up fork
Date: Fri, 08 Jul 2005 01:19:00 -0000 [thread overview]
Message-ID: <20050708011859.GB24841@trixie.casa.cgf.cx> (raw)
In-Reply-To: <42CDD3B8.69B6AB98@dessent.net>
On Thu, Jul 07, 2005 at 06:15:36PM -0700, Brian Dessent wrote:
>I think we will require a statically linked bash, or some kind of
>trickery in the rebaseall script. One potential way around this might
>be for it to output a .cmd file (or .bat under 9x, grrr) and then exec()
>$COMSPEC to run the commands. This would have the advantage of not
>requiring any Cygwin DLLs in use during the rebase, but it sounds more
>error prone and complicated.
But, the alternative of creating a version of bash just so that people
can run rebaseall sounds even more error prone.
I don't see any other foolproof way of doing this.
Btw, don't '.bat' files work on NT, too?
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2005-07-08 1:19 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 19:06 Adye, TJ (Tim)
[not found] ` <7231C15EAC2F164CA6DC326D97493C8BA1C3FA@exchange35.fed.cclr c.ac.uk>
2005-07-08 0:12 ` Larry Hall
2005-07-08 1:11 ` Brian Dessent
2005-07-08 1:19 ` Christopher Faylor [this message]
2005-07-08 1:40 ` Brian Dessent
2005-07-08 2:05 ` Eric Blake
2005-07-08 2:27 ` Brian Dessent
2005-07-08 2:38 ` Eric Blake
2005-07-08 2:54 ` Brian Dessent
2005-07-08 2:06 ` Christopher Faylor
2005-07-08 2:21 ` Igor Pechtchanski
2005-07-08 3:45 ` Christopher Faylor
2005-07-08 2:24 ` Eric Blake
2005-07-08 3:50 ` Christopher Faylor
2005-07-08 9:48 ` Gerrit P. Haase
2005-07-11 12:45 ` Jason Tishler
2005-07-12 2:08 ` Christopher Faylor
2005-07-14 12:23 ` rebaseall (was Re: Perl Win32::Shortcut screws up fork) Jason Tishler
2005-07-14 13:12 ` Dave Korn
2005-07-14 14:06 ` Brian Dessent
2005-07-14 19:57 ` Christopher Faylor
2005-07-14 14:41 ` Dave Korn
2005-07-14 15:02 ` Gerrit P. Haase
2005-07-14 15:28 ` Dave Korn
2005-07-14 15:58 ` Gerrit P. Haase
2005-07-14 16:09 ` Dave Korn
2005-07-14 15:58 ` Dave Korn
2005-07-14 20:01 ` Christopher Faylor
2005-07-15 11:29 ` Jason Tishler
2005-07-15 12:22 ` Dave Korn
2005-07-15 21:01 ` Jason Tishler
2005-07-16 0:32 ` Gerrit P. Haase
2005-07-18 13:00 ` Dave Korn
2005-07-15 14:18 ` Christopher Faylor
2005-07-16 19:08 ` Jason Tishler
2005-07-08 1:35 ` Perl Win32::Shortcut screws up fork Eric Blake
2005-07-08 2:27 ` Brian Dessent
-- strict thread matches above, loose matches on Subject: below --
2005-07-07 19:13 Adye, TJ (Tim)
2005-07-08 8:17 ` Reini Urban
2005-07-07 17:10 Adye, TJ (Tim)
[not found] ` <7231C15EAC2F164CA6DC326D97493C8BA1C3F1@exchange35.fed.cclr c.ac.uk>
2005-07-07 18:09 ` Larry Hall
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=20050708011859.GB24841@trixie.casa.cgf.cx \
--to=cgf-no-personal-reply-please@cygwin.com \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).