From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Switching to git?
Date: Sat, 22 Dec 2007 12:16:29 +0100 [thread overview]
Message-ID: <20071222111629.GA4788@thorin> (raw)
In-Reply-To: <200712220928.28355.okuji@enbug.org>
On Sat, Dec 22, 2007 at 09:28:28AM +0100, Yoshinori K. Okuji wrote:
> On Tuesday 18 December 2007 13:05, Otavio Salvador wrote:
> > > - All developers are forced to install new software and learn it (always
> > > a pain).
> >
> > Developers are used (or ought to) to learn new things since it's of
> > programming art. I guess learning wouldn't be a problem.
>
> From a theoretical point of view, you're definitely right, but the reality
> looks reverse to me. For instance, look at the inability of developers to
> editors... Even if Emacs is far superior when writing GNU-style C code, vi
> users never try to learn how to use Emacs. When it comes to command-line
> utilities vs. graphical applications, the situation is even worse.
>
> In my experience, (unfortunately) developers are too lazy to change tools.
> They change, only when they are forced or excited for some (geeky) reason.
> This includes myself.
Maybe you find interesting to know that I never use RCS (any of them) merging
feature at all. I prefer to extract patches from RCS and manage them myself.
I often even manage branches by hand as well.
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2007-12-22 12:18 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
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 [this message]
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=20071222111629.GA4788@thorin \
--to=rmh@aybabtu.com \
--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.