From: Richard Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [git migration] The problem of ChangeLog generation
Date: Tue, 13 Apr 2010 21:47:19 -0400 [thread overview]
Message-ID: <4BC51EA7.1080108@gentoo.org> (raw)
In-Reply-To: <4BC49CD5.3090208@gentoo.org>
On 04/13/2010 12:33 PM, Matti Bickel wrote:
> Alec Warner wrote:
>> Its not possible in perforce once your change has been submitted.
>
> Oh, missed that one. Maybe that makes perforce more "auditble" or whatnot.
I suspect that is the gist of it. I work with numerous systems that
have audit trails that are subject to regulation, and it is pretty
typical that the way to "correct" an audit trail entry is to add an
additional audit trail entry (with the old entry still being there -
perhaps with a pointer to the new entry). There is no shame in
admitting that you made a mistake - the kinds of people who audit these
systems look at a lack of mistakes as evidence that something is being
hidden.
Rich
next prev parent reply other threads:[~2010-04-14 1:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 2:13 [gentoo-dev] [git migration] The problem of ChangeLog generation Nirbheek Chauhan
2010-04-06 6:41 ` Fabian Groffen
2010-04-06 7:01 ` Nirbheek Chauhan
2010-04-06 11:40 ` Fabian Groffen
2010-04-07 9:58 ` Angelo Arrifano
2010-04-07 10:03 ` Ciaran McCreesh
2010-04-07 14:36 ` Richard Freeman
2010-06-21 19:34 ` [gentoo-dev] " Christian Faulhammer
2010-04-06 7:28 ` [gentoo-dev] [git migration] Proposition for tags supported by git hooks Maciej Mrozowski
2010-04-06 8:00 ` Nirbheek Chauhan
2010-04-06 13:06 ` [gentoo-dev] [git migration] The problem of ChangeLog generation Richard Freeman
2010-04-06 22:21 ` Robin H. Johnson
2010-04-07 10:05 ` Angelo Arrifano
2010-04-07 6:25 ` Hans de Graaff
2010-04-07 7:55 ` Dirkjan Ochtman
2010-04-07 16:54 ` Markos Chandras
2010-04-07 18:41 ` Nirbheek Chauhan
2010-04-07 21:54 ` Markos Chandras
2010-04-13 11:25 ` Peter Volkov
2010-04-13 11:44 ` Angelo Arrifano
2010-04-13 11:48 ` Nirbheek Chauhan
2010-04-13 13:19 ` Ulrich Mueller
2010-04-13 13:35 ` Nirbheek Chauhan
2010-04-13 16:12 ` Matti Bickel
2010-04-13 16:22 ` Angelo Arrifano
2010-04-13 16:23 ` Alec Warner
2010-04-13 16:33 ` Matti Bickel
2010-04-14 1:47 ` Richard Freeman [this message]
2010-04-14 6:39 ` Nirbheek Chauhan
2010-04-14 9:08 ` Matti Bickel
2010-04-13 16:47 ` Peter Volkov
2010-05-02 15:13 ` Jim Ramsay
2010-06-24 18:59 ` Luca Barbato
2010-06-24 20:43 ` Olivier Crête
2010-06-25 8:45 ` Peter Volkov
2010-06-25 8:49 ` Arun Raghavan
2010-06-25 9:00 ` Peter Volkov
2010-06-26 5:55 ` Olivier Crête
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=4BC51EA7.1080108@gentoo.org \
--to=rich0@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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