From: Mark Deneen <mdeneen@gmail.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Mike Christie <michaelc@cs.wisc.edu>,
Vladislav Bolkhovitin <vst@vlnb.net>,
linux-scsi@vger.kernel.org, Chetan Loke <chetanloke@gmail.com>,
linux-kernel@vger.kernel.org,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
James Bottomley <James.Bottomley@suse.de>,
scst-devel <scst-devel@lists.sourceforge.net>
Subject: Re: [Scst-devel] Fwd: Re: linuxcon 2010...
Date: Sun, 5 Sep 2010 19:13:52 -0400 [thread overview]
Message-ID: <AANLkTimdHotxVS8ZJJhg0D08FUiw4scSMTb2dryqJ_vQ@mail.gmail.com> (raw)
In-Reply-To: <1283723447.556.133.camel@haakon2.linux-iscsi.org>
On Sun, Sep 5, 2010 at 5:50 PM, Nicholas A. Bellinger
<nab@linux-iscsi.org> wrote:
>
> I think the difference between what Linus says and what he actually
> means in the above video could be easily misinterpreted, well especially
> for some non-english speaking folks. But I am certainly glad to see
> that a russian translation is also available for this google git talk
> for those who really want try to understand his reasons (and technical
> requirements) for what he is saying.
>
> So as to the specifics about why git is really the only right SCM choice
> for mainline target mode maintainership, it really all comes down to
> workflow. Does your SCM allow other people to easily and without-pain
> track your upstream subsystem tree changes and 'rebase' as necessary for
> their patch series you make improvements..? If we are talking about
> say, a single standalone driver being developed against mainline, then
> sure using a SCM like CVS or SVN is perfectly acceptable when you push
> to someone upstream like gregkh or akpm via email patch attachments.
>
> However, if we are talking about a subsystem maintainer workflow that
> requires many different people to track your subsystem tree for their
> own drivers and new feature bits, not being able to keep local branches
> for these level developers makes their life excruciatingly painful and
> unpleasent as they attempt to pull new upstream changes, especially when
> the speed of new upstream development is moving quickly. This rule
> applys even more when said subsystem has a greater scope within the
> source tree in question.
>
> Anyways, if we are going to compare SCM distributed vs. centralized
> workflow in terms of kernel projects, lets please at least compare
> apples to apples here.
>
> Best,
>
> --nab
I've been trying to keep my 2 cents out of this, as I am merely an
SCST user. Both of you have valid criticisms; the choice of SCM is
not one of them. It is nit-picking at best, especially when SCST
could switch to git easily if they so desired.
Seven years ago, would you be pushing BitKeeper?
Kind Regards,
Mark Deneen
next prev parent reply other threads:[~2010-09-05 23:13 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 14:58 [Scst-devel] Fwd: Re: linuxcon 2010 Chetan Loke
2010-08-18 15:11 ` James Bottomley
[not found] ` <AANLkTimJGxn=5kEMH68XVWqFcYG3vpfLjLjZpFGqhG_4@mail.gmail.com>
2010-08-18 15:30 ` Bart Van Assche
2010-08-18 16:04 ` Chetan Loke
2010-08-18 16:18 ` James Bottomley
2010-08-18 17:50 ` Vladislav Bolkhovitin
2010-08-19 1:18 ` jack wang
2010-08-19 21:20 ` Dirk Meister
2010-08-19 22:29 ` Nicholas A. Bellinger
2010-08-21 18:42 ` Vladislav Bolkhovitin
2010-08-21 20:25 ` Nicholas A. Bellinger
2010-08-24 18:08 ` Vladislav Bolkhovitin
2010-08-21 20:43 ` James Bottomley
2010-08-22 7:39 ` Bart Van Assche
2010-08-22 20:29 ` James Bottomley
2010-08-23 13:47 ` Joe Landman
2010-08-23 15:12 ` Bart Van Assche
[not found] ` <AANLkTim-M6dfLvJQnbieFqZCGG33E+-i+u_soCq2p9f1@mail.gmail.com>
2010-08-23 16:07 ` Chetan Loke
2010-08-23 18:03 ` Chetan Loke
2010-08-24 7:25 ` Pasi Kärkkäinen
2010-08-24 14:43 ` Linux I/O subsystem performance (was: linuxcon 2010...) Vladislav Bolkhovitin
2010-08-24 14:55 ` Matthew Wilcox
2010-08-24 17:51 ` Linux I/O subsystem performance Vladislav Bolkhovitin
2010-08-24 20:40 ` Matthew Wilcox
2010-08-24 14:55 ` [Scst-devel] Fwd: Re: linuxcon 2010 Chetan Loke
[not found] ` <4C7404C4.4040704@vlnb.net>
2010-08-24 20:31 ` Linux I/O subsystem performance (was: linuxcon 2010...) Chris Worley
2010-08-25 19:12 ` Linux I/O subsystem performance Vladislav Bolkhovitin
2010-09-16 15:05 ` Linux I/O subsystem performance (was: linuxcon 2010...) Chris Worley
2010-08-23 19:41 ` [Scst-devel] Fwd: Re: linuxcon 2010 Vladislav Bolkhovitin
2010-08-24 14:41 ` Vladislav Bolkhovitin
2010-08-24 14:51 ` Chris Weiss
2010-08-24 14:56 ` Matthew Wilcox
2010-08-25 22:20 ` Konrad Rzeszutek Wilk
2010-08-25 22:45 ` Ted Ts'o
2010-08-24 14:57 ` James Bottomley
2010-08-24 19:48 ` Vladislav Bolkhovitin
2010-08-24 21:23 ` Nicholas A. Bellinger
2010-08-26 20:11 ` Vladislav Bolkhovitin
2010-08-26 21:23 ` Nicholas A. Bellinger
2010-08-28 17:32 ` Vladislav Bolkhovitin
2010-08-28 20:47 ` Nicholas A. Bellinger
2010-08-30 20:47 ` Vladislav Bolkhovitin
2010-08-30 21:46 ` Nicholas A. Bellinger
2010-09-02 19:38 ` Vladislav Bolkhovitin
2010-09-02 20:25 ` Nicholas A. Bellinger
2010-09-05 20:18 ` Dmitry Torokhov
2010-09-05 21:50 ` Nicholas A. Bellinger
2010-09-05 23:13 ` Mark Deneen [this message]
2010-09-06 0:12 ` Nicholas A. Bellinger
2010-09-06 0:58 ` Mark Deneen
2010-09-06 1:34 ` Nicholas A. Bellinger
2010-09-06 5:04 ` Dmitry Torokhov
2010-09-05 23:41 ` Dmitry Torokhov
2010-09-05 23:59 ` Nicholas A. Bellinger
2010-09-06 4:56 ` Dmitry Torokhov
2010-09-06 10:39 ` James Bottomley
2010-09-06 11:02 ` Bart Van Assche
2010-09-06 11:27 ` James Bottomley
2010-09-06 15:26 ` Vladislav Bolkhovitin
2010-09-06 21:47 ` Vladislav Bolkhovitin
2010-09-06 21:55 ` Nicholas A. Bellinger
2010-09-06 22:14 ` david
2010-09-07 0:44 ` Dmitry Torokhov
2010-09-07 3:45 ` Chetan Loke
2010-09-07 6:15 ` Bart Van Assche
2010-09-07 6:08 ` Bart Van Assche
2010-09-07 6:26 ` Dmitry Torokhov
2010-09-07 6:29 ` Hannes Reinecke
2010-09-07 6:45 ` Bart Van Assche
2010-09-07 13:20 ` Vladislav Bolkhovitin
2010-09-07 20:14 ` Vladislav Bolkhovitin
2010-09-07 20:14 ` Vladislav Bolkhovitin
2010-09-06 21:16 ` Greg KH
2010-09-06 17:28 ` Chetan Loke
2010-09-06 21:52 ` Vladislav Bolkhovitin
2010-08-20 13:46 ` Ruben Laban
2010-08-18 17:51 ` Chetan Loke
2010-08-18 16:19 ` Bart Van Assche
2010-08-18 16:28 ` Joe Landman
2010-08-18 17:52 ` Vladislav Bolkhovitin
2010-08-18 15:12 ` Chetan Loke
2010-08-18 17:52 ` Vladislav Bolkhovitin
-- strict thread matches above, loose matches on Subject: below --
2010-08-20 17:40 Ari Lemmke
2010-08-16 16:20 Fwd: Re: [Scst-devel] " Vladislav Bolkhovitin
2010-08-17 20:30 ` James Bottomley
2010-08-18 17:52 ` Vladislav Bolkhovitin
2010-08-18 20:43 ` James Bottomley
2010-08-21 18:51 ` Vladislav Bolkhovitin
2010-08-21 20:38 ` James Bottomley
2010-08-22 22:10 ` [Scst-devel] Fwd: " Gennadiy Nerubayev
2010-08-23 16:59 ` James Bottomley
2010-08-23 17:44 ` Bart Van Assche
2010-08-23 17:58 ` James Bottomley
2010-08-23 20:11 ` Bart Van Assche
2010-08-23 20:21 ` James Bottomley
2010-08-23 19:40 ` Vladislav Bolkhovitin
2010-08-23 20:38 ` James Bottomley
2010-08-24 10:32 ` Bart Van Assche
2010-08-24 13:01 ` Chris Weiss
2010-08-24 19:53 ` Vladislav Bolkhovitin
2010-08-23 19:40 ` Vladislav Bolkhovitin
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=AANLkTimdHotxVS8ZJJhg0D08FUiw4scSMTb2dryqJ_vQ@mail.gmail.com \
--to=mdeneen@gmail.com \
--cc=James.Bottomley@suse.de \
--cc=chetanloke@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=nab@linux-iscsi.org \
--cc=scst-devel@lists.sourceforge.net \
--cc=vst@vlnb.net \
/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).