On Tue, 22 Jan 2008, ab_lists@mac.com wrote:

quoted text
> Hello there,
> 
> I have been converted to git after reading good things about it. I have been
> using it with a personal project and so I'm familiar with the basics.
> However I need to share code with a co-developer. He also has a code base that
> I need access to. For several reasons, a shared server will not work so I was
> thinking of using email to send patches back and forth.

I think bundles or email or both is likely to be the correct solution, but 
you should know that you don't need a shared server if you each have a 
server the other can read from. Each of you sets up a public repository 
with the same basic history, and you each have local clones of your public 
repository, and you pull from the other into your local clone and 
(assuming you want to accept the other's changes) you do the merge and 
push to your own public server.

In fact, having a shared server is vaguely discouraged, since it means 
there's a repository that's no single individual's responsibility; it's 
just that it's often the case that the existing social structure is based 
on a group of co-maintainers of a single series.

	-Daniel
*This .sig left intentionally blank*
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html