git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tay Ray Chuan <rctay89@gmail.com>
To: Bond <jamesbond.2k.g@gmail.com>
Cc: Michael J Gruber <git@drmicha.warpmail.net>, git@vger.kernel.org
Subject: Re: how to git with google code
Date: Sun, 28 Nov 2010 15:18:22 +0800	[thread overview]
Message-ID: <AANLkTi=1vVBiHeoYGzY+0Y6w7zXc3yhgZUHRH_v7ZauV@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimSdCOqC_nyLi4FsHPcJ+L9CnYzFK5OyQBoWUC7@mail.gmail.com>

On Sun, Nov 28, 2010 at 12:36 PM, Bond <jamesbond.2k.g@gmail.com> wrote:
> On Sun, Nov 28, 2010 at 9:57 AM, Tay Ray Chuan <rctay89@gmail.com> wrote:
>> Hi,
>> You can take "official source tree" and "Git-capable server" to be
>> your git repo that you git init-ed in your first post. But it's empty
>> isn't it? So, just skip the "git fetch" step. That leaves:
>>
>>  $ git svn clone ...
>>  $ cd trunk
>>
>> Then go on from there.
> What do I do from that is what I asked in first post of this thread?

Assuming you did

  $ git svn clone http://svn.googlecode/url/to/your/repo

You'd have a git repo that is "linked" to the Google Code svn repo.
Now go inside the git repo and do whatever you want. That was what I
thought you were looking for in this thread.

But if you need advice on "how to do stuff in git", (eg. adding files,
commit, push), just google for a git tutorial, I'm sure there are some
pretty good ones out there.

-- 
Cheers,
Ray Chuan

  reply	other threads:[~2010-11-28  7:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-26 14:20 how to git with google code Bond
2010-11-26 15:12 ` Michael J Gruber
2010-11-27  2:50   ` Bond
2010-11-28  4:27     ` Tay Ray Chuan
2010-11-28  4:36       ` Bond
2010-11-28  7:18         ` Tay Ray Chuan [this message]
2010-11-26 15:21 ` Jan Krüger

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='AANLkTi=1vVBiHeoYGzY+0Y6w7zXc3yhgZUHRH_v7ZauV@mail.gmail.com' \
    --to=rctay89@gmail.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=jamesbond.2k.g@gmail.com \
    /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).