git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: nadim khemir <nadim@khemir.net>
Cc: git@vger.kernel.org
Subject: Re: Git.pm
Date: Thu, 20 Nov 2008 09:34:46 +0100	[thread overview]
Message-ID: <20081120083446.GF10544@machine.or.cz> (raw)
In-Reply-To: <200811191856.44252.nadim@khemir.net>

  Hi,

On Wed, Nov 19, 2008 at 06:56:44PM +0100, nadim khemir wrote:
> Hi, I'm new on this mailing list and quite new to git too. I named on irc that 
> I develop mainly in Perl (http://search.cpan.org/~nkh/) when I do open 
> source. I heard that Git.pm needed some love and I can take over its 
> maintenance if there are things that need to be done.
> 
> I need to know:
> 
>         - what needs to be done
>         - who was doing maintenanace before
>         - how do you want to release it (perl modules are best placed on CPAN 
> (too))
>         - what (and who) is depending on Git.pm
>         - what would be expected of me

  I know it's quite some time since you wrote this mail originally -
have you read the Lea's thread I have recommended? What is your current
plan?

  I think the current rough consensus in the Git community is to go with
Lea's design and implementation after extending it with a nice way to
run arbitrary Git commands. This is also desirable since then we can use
her patches to make gitweb use Git.pm.

-- 
				Petr "Pasky" Baudis
People who take cold baths never have rheumatism, but they have
cold baths.

  reply	other threads:[~2008-11-20  8:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19 17:56 Git.pm nadim khemir
2008-11-20  8:34 ` Petr Baudis [this message]
2008-11-20 13:07   ` Git.pm Petr Baudis
2008-11-23 19:58   ` Git.pm nadim khemir
2008-12-07 17:39     ` Git.pm nadim khemir
2008-11-21  2:56 ` Git.pm Jakub Narebski
2008-11-23 20:09   ` Git.pm nadim khemir
  -- strict thread matches above, loose matches on Subject: below --
2012-04-26  4:15 Git.pm Subho Banerjee
2012-04-26 18:41 ` Git.pm Randal L. Schwartz
2012-04-26 18:58 ` Git.pm Tim Henigan
2012-04-26 20:10   ` Git.pm Subho Banerjee
2012-04-26 20:31     ` Git.pm Jonathan Nieder
2012-05-10 13:19       ` Git.pm Subho Banerjee
2012-05-10 15:16         ` Git.pm Jonathan Nieder
2012-05-10 15:54         ` Git.pm demerphq
2012-05-10 16:18           ` Git.pm Subho Banerjee
2012-05-10 17:22             ` Git.pm demerphq
2012-05-10 16:20           ` Git.pm Junio C Hamano
2012-05-10 17:38             ` Git.pm demerphq
2012-05-10 20:55         ` Git.pm Andrew Sayers
2012-05-11  8:27           ` Git.pm demerphq
2012-05-11 16:56         ` Git.pm Randal L. Schwartz
2012-05-11 18:10           ` Git.pm Junio C Hamano
2012-04-26 19:17 ` Git.pm Junio C Hamano
2012-04-26 19:59 ` Git.pm Sam Vilain

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=20081120083446.GF10544@machine.or.cz \
    --to=pasky@suse.cz \
    --cc=git@vger.kernel.org \
    --cc=nadim@khemir.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).