From: "Sverre Rabbelier" <alturin@gmail.com>
To: "David Aguilar" <davvid@gmail.com>
Cc: "Catalin Marinas" <catalin.marinas@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>,
git-python@googlegroups.com
Subject: Re: [StGIT PATCH 3/5] Create a git.Branch class as ancestor of stack.Stack
Date: Mon, 9 Jun 2008 02:46:18 +0200 [thread overview]
Message-ID: <bd6139dc0806081746q3b71dd3cp5dfef55184508930@mail.gmail.com> (raw)
In-Reply-To: <402731c90806081707m384edef4p4c2328ac1ee1ea08@mail.gmail.com>
On Mon, Jun 9, 2008 at 2:07 AM, David Aguilar <davvid@gmail.com> wrote:
> A few folks are working towards an OO git interface for python.
> Perhaps joining forces would be a big win for everyone?
>
> http://gitorious.org/projects/git-python
>
> It would be really cool if we could wrangle in all interested parties
> towards a common goal for python. You guys (the stgit team) have a
> lot of experience in this domain so your ideas and opinions would be
> greatly appreciated.
I very much agree with you. I'm using git-python for my GSoC project
myself (although currently I'm only using the Git object really). I
think it would be awesome if git-python and stgit.lib.git would merge.
I'd be happy to help with that in any way I can :).
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2008-06-09 0:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 21:13 [StGIT PATCH 0/5] Various updates to the new infrastructure Catalin Marinas
2008-06-04 21:13 ` [StGIT PATCH 1/5] Allow stack.patchorder.all to return hidden patches Catalin Marinas
2008-06-05 6:41 ` Karl Hasselström
2008-06-05 11:46 ` Catalin Marinas
2008-06-04 21:13 ` [StGIT PATCH 2/5] Rename Repository.head to Repository.head_ref Catalin Marinas
2008-06-05 6:46 ` Karl Hasselström
2008-06-05 11:49 ` Catalin Marinas
2008-06-05 11:58 ` Karl Hasselström
2008-06-05 12:06 ` Catalin Marinas
2008-06-05 12:46 ` Karl Hasselström
2008-06-04 21:13 ` [StGIT PATCH 3/5] Create a git.Branch class as ancestor of stack.Stack Catalin Marinas
2008-06-05 7:01 ` Karl Hasselström
2008-06-05 12:03 ` Catalin Marinas
2008-06-05 13:04 ` Karl Hasselström
2008-06-06 8:44 ` Catalin Marinas
2008-06-07 9:06 ` Karl Hasselström
2008-06-08 22:16 ` Catalin Marinas
2008-06-09 0:07 ` David Aguilar
2008-06-09 0:46 ` Sverre Rabbelier [this message]
2008-06-09 7:07 ` Karl Hasselström
2008-06-04 21:13 ` [StGIT PATCH 4/5] Add stack creation and initialisation support to lib.Stack Catalin Marinas
2008-06-05 7:28 ` Karl Hasselström
2008-06-05 12:42 ` Catalin Marinas
2008-06-07 8:59 ` Karl Hasselström
2008-06-04 21:13 ` [StGIT PATCH 5/5] Add stack creation and deletion support to the new infrastructure Catalin Marinas
2008-06-05 7:34 ` Karl Hasselström
2008-06-05 9:43 ` Catalin Marinas
2008-06-05 7:38 ` [StGIT PATCH 0/5] Various updates " Karl Hasselström
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=bd6139dc0806081746q3b71dd3cp5dfef55184508930@mail.gmail.com \
--to=alturin@gmail.com \
--cc=catalin.marinas@gmail.com \
--cc=davvid@gmail.com \
--cc=git-python@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=sverre@rabbelier.nl \
/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).