From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: git newbie errors
Date: Wed, 10 Nov 2010 15:02:36 +0100 [thread overview]
Message-ID: <yb039r9mg3n.fsf@dod.no> (raw)
In-Reply-To: <m2mxphqodu.fsf@gmail.com>
>>>>> Francis Moreau <francis.moro@gmail.com>:
> It sum up how *distributed* workflows works.
I'm in a maze of "distributed" commits, all alike.
I believe it is important that different people's changes are run
together as soon as possible.
I like continous integration building (from changes contributed by
different developers).
I don't like the need for a person that is the designated integrator.
(I didn't look at the man page. Give me a URL or give me death!)
next prev parent reply other threads:[~2010-11-10 14:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 18:09 Lars Magne Ingebrigtsen
2010-11-09 18:52 ` Steinar Bang
2010-11-09 18:56 ` Julien Danjou
2010-11-09 19:07 ` Lars Magne Ingebrigtsen
2010-11-09 21:12 ` Andreas Schwab
2010-11-09 20:19 ` Francis Moreau
2010-11-09 20:36 ` Steinar Bang
2010-11-10 13:50 ` Francis Moreau
2010-11-10 14:02 ` Steinar Bang [this message]
2010-11-12 0:01 ` Greg Troxel
2010-11-10 2:15 ` Katsumi Yamaoka
2010-11-10 17:38 ` Andreas Schwab
2010-11-10 17:56 ` Lars Magne Ingebrigtsen
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=yb039r9mg3n.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@gnus.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).