git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@MIT.EDU>
To: Annard Brouwer <ab_lists@mac.com>
Cc: Daniel Barkalow <barkalow@iabervon.org>, git@vger.kernel.org
Subject: Re: Using email between 2 developers to keep git repositories in sync
Date: Tue, 22 Jan 2008 17:59:02 -0500	[thread overview]
Message-ID: <20080122225902.GE1659@mit.edu> (raw)
In-Reply-To: <2D91636D-197A-41C8-8BB3-D5002135BF99@mac.com>

On Tue, Jan 22, 2008 at 11:52:40PM +0100, Annard Brouwer wrote:
> Thank you all for your suggestions! The problem is that each of us having a 
> local server accessible to the other is not possible. Therefore I will 
> follow the path of sending patches by email and on releases we can 
> synchronise using bundles. I think that's the best fit for our model of 
> developing code semi-independently.

Is your project an open source one, or one where you don't mind the
source code being made public?  If so, another easier solution would
be to use a git hosting service, such as what is available at
http://repo.or.cz.

I'd also suggest synchronizing with bundles much more frequently than
at release points.  The problem with sending patches back and forth is
it's very easy to make a mistake, and also, as far as git is
concerned, each patch is a separate changeset applied in two places.
So it makes merging more challenging for git.  It can probably handle
it, but makes life harder for everyone concerned.  So if you can use a
site like repo.or.cz, I'd highly recommend it.

						- Ted

      reply	other threads:[~2008-01-22 22:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22 12:47 Using email between 2 developers to keep git repositories in sync ab_lists
2008-01-22 13:00 ` Johannes Schindelin
2008-01-22 13:53   ` Jakub Narebski
2008-01-22 14:35     ` Mark Levedahl
2008-01-22 15:05       ` ab_lists
2008-01-22 16:00         ` Mark Levedahl
2008-01-22 22:22 ` Daniel Barkalow
2008-01-22 22:52   ` Annard Brouwer
2008-01-22 22:59     ` Theodore Tso [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=20080122225902.GE1659@mit.edu \
    --to=tytso@mit.edu \
    --cc=ab_lists@mac.com \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).