From: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
To: James Pickens <jepicken@gmail.com>
Cc: Peter Harris <git@peter.is-a-geek.org>, Git ML <git@vger.kernel.org>
Subject: Re: Disallow amending published commits?
Date: Sun, 22 Mar 2009 16:15:08 +0100 [thread overview]
Message-ID: <20090322151508.GA13577@vidovic> (raw)
In-Reply-To: <885649360903212109v316f441fvea3f498e91c0059e@mail.gmail.com>
On Sat, Mar 21, 2009 at 09:09:43PM -0700, James Pickens wrote:
> I think you understood the question perfectly, and your comments all make
> sense. Perhaps I'm just being paranoid and this won't be a problem at all.
I guess it's most depending of your proposed general workflow. So, it
makes sense.
> A bit of background might help explain my paranoia: I'm about to pilot Git
> on a fairly large project, where none of the users have Git experience, and
> many of them don't have much experience with any other version control
> system either.
As I understand, a part of your workflow is based on automatic testing
stages. It could be a good thing but I think you have to fit this into a
more general "human based worflow". I mean that parallel developments
should have one or more "official maintainers". Maintainers would have
to care of the history integrity, assume the responsability of passing
the tests, etc.
IMHO, good maintainers you can trust is much better than any "more
automatic restrictive testing suites".
Here is a link talking about that kind of issues that you (and your
maintainers) may be interested in:
http://kerneltrap.org/Linux/Git_Management
--
Nicolas Sebrecht
next prev parent reply other threads:[~2009-03-22 15:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 17:56 Disallow amending published commits? James Pickens
2009-03-21 18:46 ` Peter Harris
2009-03-21 22:49 ` James Pickens
2009-03-22 1:53 ` Peter Harris
2009-03-22 2:57 ` Peter Harris
2009-03-22 4:09 ` James Pickens
2009-03-22 14:19 ` Peter Harris
2009-03-22 15:15 ` Nicolas Sebrecht [this message]
2009-03-22 2:42 ` Jeff King
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=20090322151508.GA13577@vidovic \
--to=nicolas.s-dev@laposte.net \
--cc=git@peter.is-a-geek.org \
--cc=git@vger.kernel.org \
--cc=jepicken@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 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).