From: Rustom Mody <rustompmody@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: git workflow for fully distributed mini-teams
Date: Wed, 16 Sep 2009 13:05:05 +0530 [thread overview]
Message-ID: <f46c52560909160035o6b09800eh5219d49e7569cf23@mail.gmail.com> (raw)
I am trying to formulate (and understand) what it means to have a
fully-distributed mini team workflow with git.
By fully distributed I mean theres no central repo -- not for pushing
or even pulling; all communication is by email.
By mini-team I mean: Not more than 5 programmers.
Heres a typical scenario.
There are 3 programmers A B and C who communicate by email who have
started off from the same code base.
A's branches: dev, master, B, C
B's branches: dev, master, A, C
C's branches: dev, master, A, B
A's best practices (and invariants) are:
I (ie A) develop on dev (or other topic branches).
I only merge onto master; never commit.
I never work on nor merge onto B and C.
When B sends me patches I apply them to the B branch likewise for C.
Thereafter I merge that branch onto dev or master.
There are no tracking branches because there are no remotes -- no
central repo. [not clear about this]
B and C have corresponding practices/behavior.
So the questions...
Is there a better way of doing things?
Can some of these practices/invariants be enforced by scripts/options etc?
What about checkpointing and restoring from botches?
next reply other threads:[~2009-09-16 7:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 7:35 Rustom Mody [this message]
2009-09-16 16:43 ` git workflow for fully distributed mini-teams Nicolas Sebrecht
2009-09-17 7:03 ` Rustom Mody
2009-09-17 7:28 ` Johannes Sixt
2009-09-17 12:38 ` Rustom Mody
2009-09-17 13:52 ` Rustom Mody
2009-09-17 14:47 ` Johannes Sixt
2009-09-18 7:01 ` Rustom Mody
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=f46c52560909160035o6b09800eh5219d49e7569cf23@mail.gmail.com \
--to=rustompmody@gmail.com \
--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).