From: Peter Harris <git@peter.is-a-geek.org>
To: James Pickens <jepicken@gmail.com>
Cc: Git ML <git@vger.kernel.org>
Subject: Re: Disallow amending published commits?
Date: Sun, 22 Mar 2009 10:19:41 -0400 [thread overview]
Message-ID: <eaa105840903220719g6af88db1xccf9fba20c573570@mail.gmail.com> (raw)
In-Reply-To: <885649360903212109v316f441fvea3f498e91c0059e@mail.gmail.com>
On Sun, Mar 22, 2009 at 12:09 AM, 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.
>
> 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. I had to fight hard to get this pilot approved, and a lot
> of people will be watching to see how it goes, so I'm trying to do anything
> I can to make sure it will be successful.
Ah, yes. I can understand your paranoia.
Most new users will stick to your 'cheat sheet', and never even do
enough research to learn that you can amend existing history, much
less try it. A few will dig through the docs and try everything at
least once. I admit it; I fall into the latter category. :-)
Peter Harris
next prev parent reply other threads:[~2009-03-22 14:21 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 [this message]
2009-03-22 15:15 ` Nicolas Sebrecht
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=eaa105840903220719g6af88db1xccf9fba20c573570@mail.gmail.com \
--to=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).