From: "Bryan Donlan" <bdonlan@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: thread-safe libgit.a as a GSoC project, was Re: [SoC RFC] libsvn-fs-git: A git backend for the subversion filesystem
Date: Mon, 24 Mar 2008 15:50:04 -0400 [thread overview]
Message-ID: <3e8340490803241250w186d6ae2l38031521c2d5c6c2@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.1.00.0803221229410.4124@racer.site>
On Sat, Mar 22, 2008 at 7:35 AM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Sat, 22 Mar 2008, Bryan Donlan wrote:
>
> > On Wed, Mar 19, 2008 at 12:08 AM, Bryan Donlan <bdonlan@gmail.com> wrote:
> >
> > > I'm planning to apply for the git summer of code project. My proposal
> > > is based on the project idea of a subversion gateway for git,
> > > implemented with a new subversion filesystem layer. A draft of my
> > > proposal follows; I'd appreciate any comments/questions on it before
> > > the application period proper begins.
> >
> > Thanks for all the comments. To try to avoid spamming the list, I've
> > replied in a single message, if it'd be better to reply individually
> > in the future please let me know.
>
> My preference is to have single replies, possibly changing the subject
> ("xyz, was Re: blabla"), but it is maybe just me.
>
> > Also, after looking at libgit in a bit more detail, I think it might be
> > necessary to not use it after all, as subversion requires support for
> > multiple open repositories, as well as thread safety (at least when
> > accessing different open repo from different threads). Perhaps a
> > thread-safe git library would be a nice SoC project as well?
>
> As I said on IRC yesterday, I think that such a libgit.a would be nice,
> _but_
>
> - a lot of git programs expect to be one-shot, and libgit.a shows that,
>
> - not many people will help you with your effort, but just ignore it and
> actively introduce things that do not help libification (at least that's
> my experience),
>
> - unless you have a proper need for such a library, I do not think there
> is enough motivation to actually get it to completion.
>
> I once thought that libification would be nice, and important, but as I do
> not need it myself, I reversed my opinion.
All right. If I do end up having to recreate (thread-safe,
multiple-git-dir-safe) logic for my project, I'll try to keep in mind
the possibility of spinning it off into a proper library later though
:)
prev parent reply other threads:[~2008-03-24 19:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 4:08 [SoC RFC] libsvn-fs-git: A git backend for the subversion filesystem Bryan Donlan
2008-03-20 4:31 ` Sam Vilain
2008-03-20 4:56 ` Shawn O. Pearce
2008-03-20 6:18 ` Harvey Harrison
2008-03-20 9:22 ` Julian Phillips
2008-03-20 10:01 ` Jakub Narebski
2008-03-22 5:02 ` Bryan Donlan
2008-03-22 11:35 ` thread-safe libgit.a as a GSoC project, was " Johannes Schindelin
2008-03-23 1:34 ` Govind Salinas
2008-03-23 2:10 ` Johannes Schindelin
2008-03-24 19:50 ` Bryan Donlan [this message]
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=3e8340490803241250w186d6ae2l38031521c2d5c6c2@mail.gmail.com \
--to=bdonlan@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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.
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).