From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Govind Salinas <blix@sophiasuchtig.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] Pyrite project.
Date: Sat, 26 Jan 2008 17:50:31 +0000 (GMT) [thread overview]
Message-ID: <alpine.LSU.1.00.0801261749000.23907@racer.site> (raw)
In-Reply-To: <5d46db230801260937w3a514842t3943d0bd7c8dfb70@mail.gmail.com>
Hi,
On Sat, 26 Jan 2008, Govind Salinas wrote:
> On 1/26/08, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
>
> > On Sat, 26 Jan 2008, Govind Salinas wrote:
> >
> > > On 1/26/08, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > >
> > > > Govind wrote:
> > > >
> > > > > 3. Start stripping away non-performance-critical C code and
> > > > > convert it to python code to help interoperate with
> > > > > extensions and GUIs
> > > >
> > > > I am absolutely no fan of "extensions". You keep breaking other
> > > > people's code if your core introduces changes; see for example the
> > > > libgit.a issue with cgit.
> > >
> > > The nice thing about extensions is that you don't have to use them
> > > if you don't want to.
> >
> > I know what the nice thing about extensions is. My point was that
> > there is also a pretty nasty side. One that I am not prepared to
> > accept easily.
>
> There is another benefit too. Have a bit of code that might be
> dangerous? Put it in an extension and it can be tested in isolation,
> without the need to rebuild the project (for people that offer to test
> for you). Once it is ready and tested for general use, it can
> beincorporated into the standard.
We have branches for that. We don't even need an extension mechanism.
Ciao,
Dscho
next prev parent reply other threads:[~2008-01-26 17:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 9:27 [ANNOUNCE] Pyrite project Govind Salinas
2008-01-26 11:17 ` Jakub Narebski
2008-01-26 16:16 ` Govind Salinas
2008-01-26 13:21 ` Johannes Schindelin
[not found] ` <5d46db230801260842i89db074u29657c22f6dbedef@mail.gmail.com>
[not found] ` <alpine.LSU.1.00.0801261654410.23907@racer.site>
2008-01-26 17:37 ` Govind Salinas
2008-01-26 17:50 ` Johannes Schindelin [this message]
[not found] ` <5d46db230801261453q5d877e4eva8adbb5bc233bb75@mail.gmail.com>
[not found] ` <5d46db230801261455u1d27979ex662366f7abaee6fa@mail.gmail.com>
2008-01-26 22:58 ` Govind Salinas
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LSU.1.00.0801261749000.23907@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=blix@sophiasuchtig.com \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).