From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Marco Costalba <mcostalba@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: duplicated include files
Date: Sun, 04 Nov 2007 15:20:48 -0800 [thread overview]
Message-ID: <472E53D0.2000204@goop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0711041447330.6072@localhost.localdomain>
Robert P. J. Day wrote:
> actually, one wonders if there's any value in keeping any references
> to other version control systems such as subversion, SCCS, CVS,
> mercurial, etc.
>
What do you mean by "other"? git doesn't have a monopoly, and the
kernel should support people using a reasonable set of version control
systems. Supporting VSS would be strange, but nothing wrong with the
set you listed, if people find those systems useful. It's not like it
amounts to a huge amount of effort to do so.
J
next prev parent reply other threads:[~2007-11-04 23:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 19:41 duplicated include files Marco Costalba
2007-11-04 19:43 ` Marco Costalba
2007-11-04 19:49 ` Robert P. J. Day
2007-11-04 23:20 ` Jeremy Fitzhardinge [this message]
2007-11-05 3:49 ` Robert P. J. Day
2007-11-04 23:43 ` Bernd Petrovitsch
2007-11-04 19:51 ` Randy Dunlap
2007-11-05 10:51 ` Geert Uytterhoeven
2007-11-05 11:38 ` Marco Costalba
2007-11-14 20:40 ` Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2007-11-04 17:31 Robert P. J. Day
2007-11-04 18:07 ` Randy Dunlap
2007-11-04 18:37 ` Robert P. J. Day
2007-11-04 18:46 ` Randy Dunlap
2007-11-04 19:03 ` Adrian Bunk
2007-11-04 19:10 ` Robert P. J. Day
2007-11-05 3:02 ` Paul Mundt
2007-11-05 8:27 ` Geert Uytterhoeven
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=472E53D0.2000204@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcostalba@gmail.com \
--cc=rpjday@crashcourse.ca \
/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.