From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Dropping Git.pm (at least Git.xs)?
Date: Thu, 7 Sep 2006 21:51:07 +0200 [thread overview]
Message-ID: <20060907195107.GD23891@pasky.or.cz> (raw)
In-Reply-To: <7vodtxuqt4.fsf@assigned-by-dhcp.cox.net>
Hi,
Dear diary, on Sun, Sep 03, 2006 at 01:34:31PM CEST, I got a letter
where Junio C Hamano <junkio@cox.net> said that...
> - I think the clean-up promise of Git.pm is great (e.g.
> safe_qx should be part of it not in git-svn alone).
>
> - I think Git.xs was a bit premature and raised the hurdle of
> cleaning up and consolidating various core-wrappers from
> existing Perl scripts into Git.pm and have them use Git.pm.
> It would be nice if we can drop this part for now, and do a
> bit more Perl-level clean-up first.
>
> - I think "repository" abstraction, if we are going to have
> one, should be designed from the core level if we are going
> to have it accessible from Git.xs. Unfortunately I am not
> ready to invest great time and effort for core level
> libification at this moment.
I basically agree on all three points - I will try to submit a patch
to implement get_object() purely in Git.pm reasonably soon, and will see
about introducing some actually designed repository division abstraction
when I get some time. I hope to see Git.xs come back again in few
months, but for now I have to concur that we should go back to the
drawing board.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Snow falling on Perl. White noise covering line noise.
Hides all the bugs too. -- J. Putnam
prev parent reply other threads:[~2006-09-07 19:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-03 11:34 Dropping Git.pm (at least Git.xs)? Junio C Hamano
2006-09-03 15:03 ` Dennis Stosberg
2006-09-10 17:59 ` Sam Vilain
2006-09-10 22:13 ` Jakub Narebski
2006-09-11 3:25 ` Petr Baudis
2006-09-11 8:58 ` Jakub Narebski
2006-09-07 19:51 ` Petr Baudis [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=20060907195107.GD23891@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).