From: Pavel Roskin <proski@gnu.org>
To: "The development of GRUB 2" <grub-devel@gnu.org>,
"Vesa Jääskeläinen" <chaac@nic.fi>
Subject: Re: Switching to git?
Date: Tue, 18 Dec 2007 16:32:20 -0500 [thread overview]
Message-ID: <1198013540.19477.31.camel@dv> (raw)
In-Reply-To: <476811A8.4010007@nic.fi>
On Tue, 2007-12-18 at 20:30 +0200, Vesa Jääskeläinen wrote:
> Just leave cygwin out of the box... thank you!
>
> cygwin is one of the worst pieces of software that just does not work
> correctly.
I wonder if you have actually used the native Windows port of CVS.
> In my point-of-view portability means that you can use
> software natively on some platform and it does not include installing
> emulators or such to run software (like cygwin, wine).
OK, I just checked grub4dos sources, and it looks like that it should be
compiled either under Linux or in Cygwin. Look at the "build" script
written specifically for grub4dos - it's a shell script. If the build
system was using native tools like Visual C or even MinGW, we would see
very different build scripts.
Therefore, I don't see how native Windows portability of the version
control system can be an issue for GRUB.
Speaking of Cygwin, my experience with it has been much more positive,
especially if it's installed for one specific purpose like compiling
some project (as opposed to a playground for UNIX wannabees). I don't
think it's a requirement that is going to deter anyone from working on
GRUB.
The work on the native git is underway. Many scripts have been replaced
with C sources. I expect that effort to be completed before GRUB
actually needs that (i.e. before it compiles with Visual C or another
non-Cygwin Windows compiler).
And if you need any GUI, qgit is a native Windows application compiled
with Qt4. The "Tortoise" like GUI doesn't make much sense for git, as
it's file oriented, and git is changeset oriented. The Eclipse plugin
(egit) is available.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2007-12-18 21:32 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 17:45 Switching to git? Pavel Roskin
2007-12-06 18:04 ` Otavio Salvador
2007-12-07 1:42 ` willem
2007-12-07 11:43 ` Otavio Salvador
2007-12-08 5:39 ` willem
2007-12-08 0:06 ` Vesa Jääskeläinen
2007-12-08 1:16 ` Otavio Salvador
2007-12-08 2:54 ` Pavel Roskin
2007-12-12 14:30 ` Robert Millan
2007-12-12 15:03 ` Otavio Salvador
2007-12-12 16:21 ` Amin Azez
2007-12-12 15:36 ` Pavel Roskin
2007-12-12 16:01 ` Robert Millan
2007-12-15 10:54 ` Robert Millan
2007-12-16 4:32 ` Otavio Salvador
2007-12-16 11:03 ` Robert Millan
2007-12-16 17:21 ` Pavel Roskin
2007-12-17 7:02 ` Yoshinori K. Okuji
2007-12-17 11:11 ` Markus Elfring
2007-12-17 23:53 ` willem
2007-12-17 11:40 ` Tomáš Ebenlendr
2007-12-17 12:20 ` Markus Elfring
2007-12-17 11:58 ` Otavio Salvador
2007-12-18 0:10 ` willem
2007-12-18 1:20 ` Pavel Roskin
2007-12-18 2:04 ` Otavio Salvador
2007-12-18 2:57 ` Yoshinori K. Okuji
2007-12-18 12:05 ` Otavio Salvador
2007-12-18 18:30 ` Vesa Jääskeläinen
2007-12-18 21:32 ` Pavel Roskin [this message]
2007-12-21 17:54 ` Vesa Jääskeläinen
2007-12-19 0:11 ` Gregg C Levine
2007-12-22 8:28 ` Yoshinori K. Okuji
2007-12-22 11:16 ` Robert Millan
2007-12-23 4:58 ` Pavel Roskin
2008-01-04 17:06 ` Jeroen Dekkers
2008-01-04 17:39 ` Otavio Salvador
2007-12-18 16:29 ` Pavel Roskin
2007-12-22 8:50 ` Yoshinori K. Okuji
2007-12-22 11:20 ` Robert Millan
2007-12-22 12:28 ` Yoshinori K. Okuji
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=1198013540.19477.31.camel@dv \
--to=proski@gnu.org \
--cc=chaac@nic.fi \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.