public inbox for gnap-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Philipp Riegger <lists@anderedomain.de>
To: gnap-dev@lists.gentoo.org
Subject: Re: [gnap-dev] I'm Back: GSoC and repos move
Date: Wed, 14 May 2008 11:19:49 +0200	[thread overview]
Message-ID: <1210756789.4099.2.camel@troy.riegger.name> (raw)
In-Reply-To: <1210754040.19238.2.camel@alice.wonderland>

On Wed, 2008-05-14 at 10:34 +0200, JoseAlberto wrote:
> I'm back, after a long time out (i was working in a big company
> project) so now is the moment.

Great to have you back.
> 
> The first step is easy, we will move all our code to google code. Any
> objection?

Not sure. I think, git might be interesting, too, since it supports user
contribution better. But then we'd have to learn how to use git. But if
we used git, we could get a repo on gentoo infrastructure.
> 
Philipp

-- 
gnap-dev@lists.gentoo.org mailing list



      parent reply	other threads:[~2008-05-14  9:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14  8:34 [gnap-dev] I'm Back: GSoC and repos move JoseAlberto
2008-05-14  9:10 ` Andrey Falko
2008-05-14  9:19 ` Philipp Riegger [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=1210756789.4099.2.camel@troy.riegger.name \
    --to=lists@anderedomain.de \
    --cc=gnap-dev@lists.gentoo.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