From: "Sverre Rabbelier" <alturin@gmail.com>
To: "Peter Farmer" <pfarmer@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Develop with git on a Google Code project
Date: Wed, 28 May 2008 10:39:38 +0200 [thread overview]
Message-ID: <bd6139dc0805280139q349be164yd91a6de3f870523d@mail.gmail.com> (raw)
In-Reply-To: <6944de040805202225r2d7d0a75y5179b60556cfa283@mail.gmail.com>
On Wed, May 21, 2008 at 7:25 AM, Peter Farmer <pfarmer@gmail.com> wrote:
> Saw this this morning,
>
> http://google-opensource.blogspot.com/2008/05/develop-with-git-on-google-code-project.html
>
> You can't beat a bit of exposure!
There's been a follow up.
http://google-opensource.blogspot.com/2008/05/export-git-project-to-google-code.html
I wonder what the list thinks of the things described there, I get the
feeling that there's some things done there that are Not Recommended
(TM) and some that are just more complicated than they have to be.
Perhaps the list could have a look at the post and send in comments,
the post seems like bad advertising to me :P.
--
Cheers,
Sverre Rabbelier
prev parent reply other threads:[~2008-05-28 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 5:25 Develop with git on a Google Code project Peter Farmer
2008-05-21 8:20 ` Johannes Schindelin
2008-05-28 8:39 ` Sverre Rabbelier [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=bd6139dc0805280139q349be164yd91a6de3f870523d@mail.gmail.com \
--to=alturin@gmail.com \
--cc=git@vger.kernel.org \
--cc=pfarmer@gmail.com \
--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).