From: Johannes Sixt <j.sixt@viscovery.net>
To: Rustom Mody <rustompmody@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git workflow for fully distributed mini-teams
Date: Thu, 17 Sep 2009 09:28:20 +0200 [thread overview]
Message-ID: <4AB1E514.9030501@viscovery.net> (raw)
In-Reply-To: <f46c52560909170003l61a2e1a3kf62c94ffd7ed9710@mail.gmail.com>
Rustom Mody schrieb:
> I am really concerned about things like:
>
> A commited something on the B branch, received a patch from B. That
> patch did not apply (or worse it applied -- on top of A's!)
> So ideally there should be an option that says (when A is on B branch
> and tries to commit) "Sorry buddy -- No commits here!"
I think the most important thing would be that you send bundles around,
not patches, so that you all can work with and talk about unique object names.
-- Hannes
next prev parent reply other threads:[~2009-09-17 7:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 7:35 git workflow for fully distributed mini-teams Rustom Mody
2009-09-16 16:43 ` Nicolas Sebrecht
2009-09-17 7:03 ` Rustom Mody
2009-09-17 7:28 ` Johannes Sixt [this message]
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=4AB1E514.9030501@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=rustompmody@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.