From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Igor Bukanov" <igor.bukanov@gmail.com>
Cc: "Pavel Roskin" <proski@gnu.org>,
"Shawn Pearce" <spearce@spearce.org>,
"Keith Packard" <keithp@keithp.com>,
git@vger.kernel.org
Subject: Re: Importing Mozilla CVS into git
Date: Wed, 7 Jun 2006 11:30:40 -0400 [thread overview]
Message-ID: <9e4733910606070830g24a08771i1a332552a95283d1@mail.gmail.com> (raw)
In-Reply-To: <df0b33100606070202w581ff581i435056f0fbc197f8@mail.gmail.com>
On 6/7/06, Igor Bukanov <igor.bukanov@gmail.com> wrote:
> On 6/2/06, Jon Smirl <jonsmirl@gmail.com> wrote:
> > On 6/2/06, Pavel Roskin <proski@gnu.org> wrote:
> > > Dependency on Cygwin, Perl and Python is too much. Windows is becoming
> > > a legacy system in some circles, and it may run on legacy hardware. Yet
> > > it's irreplaceable as a testing platform for many projects.
> >
> > 80% of Mozilla commiters are running Windows. Some are OS bilingual
> > but many are not.
>
> Mozilla build system on Windows requires Cygwin and there are 198 Perl
> files in Firefox tree. So it is only Python that can be problematic.
Other people have sent me mail saying this may not be as big as
problem as was thought, only documentation people on WIndows may be an
issues.
>
> Regards, Igor
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2006-06-07 15:30 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 22:21 Importing Mozilla CVS into git Jon Smirl
2006-06-01 23:20 ` Keith Packard
2006-06-02 0:55 ` Jon Smirl
2006-06-02 2:07 ` Keith Packard
2006-06-02 2:36 ` Jon Smirl
2006-06-02 2:56 ` Shawn Pearce
2006-06-02 3:39 ` Keith Packard
2006-06-02 3:47 ` Jon Smirl
2006-06-02 3:55 ` Keith Packard
2006-06-02 4:00 ` Jon Smirl
2006-06-02 4:11 ` Shawn Pearce
2006-06-02 4:39 ` Pavel Roskin
2006-06-02 4:44 ` Shawn Pearce
2006-06-02 7:46 ` Johannes Schindelin
2006-06-02 4:44 ` Jon Smirl
2006-06-07 9:02 ` Igor Bukanov
2006-06-07 15:21 ` Pavel Roskin
2006-06-07 15:30 ` Jon Smirl [this message]
2006-06-07 15:58 ` Jakub Narebski
2006-06-07 16:17 ` Linus Torvalds
2006-06-07 18:29 ` Martin Langhoff
2006-06-02 4:16 ` Martin Langhoff
2006-06-03 23:16 ` Robin Rosenberg (list subscriber)
2006-06-03 23:47 ` Linus Torvalds
2006-06-04 2:24 ` Bertrand Jacquin
2006-06-04 7:05 ` Jakub Narebski
2006-06-04 17:55 ` Linus Torvalds
2006-06-04 19:44 ` Robin Rosenberg (list subscriber)
2006-06-04 20:00 ` Linus Torvalds
2006-06-04 21:25 ` Robin Rosenberg (list subscriber)
2006-06-04 22:02 ` Robin Rosenberg (list subscriber)
2006-06-04 23:19 ` Linus Torvalds
2006-06-05 0:10 ` Yakov Lerner
2006-06-03 0:09 ` Jon Smirl
2006-06-03 4:28 ` Jon Smirl
2006-06-06 5:55 ` Martin Langhoff
2006-06-06 15:13 ` Jon Smirl
2006-06-06 19:57 ` Martin Langhoff
2006-06-07 0:12 ` Keith Packard
2006-06-07 0:40 ` Jon Smirl
2006-06-01 23:48 ` Linus Torvalds
2006-06-02 0:59 ` Jon Smirl
2006-06-02 1:11 ` Linus Torvalds
2006-06-02 6:40 ` Junio C Hamano
2006-06-02 15:53 ` Linus Torvalds
2006-06-02 16:00 ` Junio C Hamano
2006-06-02 4:14 ` Martin Langhoff
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=9e4733910606070830g24a08771i1a332552a95283d1@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=git@vger.kernel.org \
--cc=igor.bukanov@gmail.com \
--cc=keithp@keithp.com \
--cc=proski@gnu.org \
--cc=spearce@spearce.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).