From: "David S. Miller" <davem@redhat.com>
To: xavier.bestel@free.fr
Cc: dent@cosy.sbg.ac.at, alan@lxorguk.ukuu.org.uk,
tori@ringstrom.mine.nu, imipak@yahoo.com,
linux-kernel@vger.kernel.org
Subject: Re: Linux crypto?
Date: Fri, 24 May 2002 14:43:05 -0700 (PDT) [thread overview]
Message-ID: <20020524.144305.88932392.davem@redhat.com> (raw)
In-Reply-To: <1022276970.4174.153.camel@bip>
From: Xavier Bestel <xavier.bestel@free.fr>
Date: 24 May 2002 23:49:29 +0200
Why ? You can make all edits you like, they just won't be folded back to
their tree. You can retrieve all their fixes, just if you have an
important change to do in their core, do it as free speech on their
public mailing list, do not provide a patch.
I can't edit their code because effectively I could contaminate
their sources.
Say I make some global networking API change, and this required
a significant edit to ipsec to make it comply with the new
structure layout or whatever.
And let's assume there is only one clear way to implement the
change, no other way to do the change would make any sense at all.
So the IPSEC people would have to effectively avoid integrating my
change, ie. it is a big onus on them to make their version of the API
update different enough from my edits so that nobody can claim they
just applied my change.
And the fact that there would be two edits makes no sense. If a
change has to occur twice in two different ways this makes merging a
disaster.
So someone quips "just let them edit and just merge from IPSEC" and
I say I refuse to let something just sit in the tree that I cannot
edit when I want to make sweeping changes across the tree. That is
unacceptable.
next prev parent reply other threads:[~2002-05-24 21:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 18:03 Linux crypto? Myrddin Ambrosius
2002-05-22 18:38 ` Alan Cox
2002-05-23 8:45 ` Trond Myklebust
2002-05-23 21:46 ` Tobias Ringstrom
2002-05-24 14:58 ` Alan Cox
2002-05-24 17:32 ` Thomas 'Dent' Mirlacher
2002-05-24 17:21 ` David S. Miller
2002-05-24 17:42 ` Thomas 'Dent' Mirlacher
2002-05-24 17:31 ` David S. Miller
2002-05-24 17:57 ` Thomas 'Dent' Mirlacher
2002-05-24 19:18 ` Myrddin Ambrosius
2002-05-25 4:01 ` Henrique de Moraes Holschuh
2002-05-24 18:41 ` Alan Cox
2002-05-24 18:30 ` Thomas 'Dent' Mirlacher
2002-05-24 18:55 ` Alan Cox
2002-05-24 18:50 ` Sandy Harris
2002-05-29 0:24 ` Petro
2002-05-24 20:17 ` Myrddin Ambrosius
2002-05-24 21:25 ` Thomas 'Dent' Mirlacher
2002-05-24 18:45 ` Herman Oosthuysen
2002-05-24 21:49 ` Xavier Bestel
2002-05-24 21:43 ` David S. Miller [this message]
2002-05-26 10:06 ` Jakob Østergaard
2002-06-18 15:06 ` Drivers, Hardware, and their relationship to Bagels Myrddin Ambrosius
2002-06-18 15:01 ` Zwane Mwaikambo
2002-06-18 15:26 ` Richard B. Johnson
2002-06-18 18:35 ` Myrddin Ambrosius
2002-06-18 19:13 ` Richard B. Johnson
2002-06-19 2:11 ` Stevie O
2002-06-18 16:01 ` Xavier Bestel
2002-06-18 18:23 ` Myrddin Ambrosius
-- strict thread matches above, loose matches on Subject: below --
2002-05-28 18:28 Linux crypto? James Yonan
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=20020524.144305.88932392.davem@redhat.com \
--to=davem@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dent@cosy.sbg.ac.at \
--cc=imipak@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tori@ringstrom.mine.nu \
--cc=xavier.bestel@free.fr \
/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