From: Jakub Narebski <jnareb@gmail.com>
To: Paul Richards <paul.richards@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How to manage multiple personal projects
Date: Wed, 15 Jul 2009 10:45:32 -0700 (PDT) [thread overview]
Message-ID: <m3ws69u9g0.fsf@localhost.localdomain> (raw)
In-Reply-To: <a1138db30907150900j7d6152ebs755d83adf7717287@mail.gmail.com>
Paul Richards <paul.richards@gmail.com> writes:
[...]
> I believe the correct choice with Git is to create a repository per
> project. This would work OK for me, but I worry about the shear
> number of repositories I'd end up creating. Part of the nice thing
> with my current Subversion setup is that starting a new project is
> very easy and cheap, I don't create a new repository each time.
[...]
Perhaps 'repo' tool developed by Google will be what you want?
http://android.git.kernel.org/?p=tools/repo.git
http://newblogtopic.blogspot.com/2008/11/gerrit-and-repo-android-source_04.html
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2009-07-15 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 16:00 How to manage multiple personal projects Paul Richards
2009-07-15 16:39 ` Avery Pennarun
2009-07-15 17:45 ` Jakub Narebski [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=m3ws69u9g0.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=paul.richards@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).