From owner-freebsd-audit Mon Jul 2 19:17:53 2001 Delivered-To: freebsd-audit@freebsd.org Received: from coffee.q9media.com (coffee.q9media.com [216.94.229.19]) by hub.freebsd.org (Postfix) with ESMTP id 1496D37B405 for ; Mon, 2 Jul 2001 19:17:51 -0700 (PDT) (envelope-from mike@coffee.q9media.com) Received: (from mike@localhost) by coffee.q9media.com (8.11.2/8.11.2) id f632Vgu06246; Mon, 2 Jul 2001 22:31:43 -0400 (EDT) (envelope-from mike) Date: Mon, 2 Jul 2001 22:31:43 -0400 (EDT) Message-Id: <200107030231.f632Vgu06246@coffee.q9media.com> To: Kris Kennaway From: Mike Barcroft Cc: Dima Dorfman , Warner Losh , audit@FreeBSD.org Subject: Re: Committing patches submitted here Sender: owner-freebsd-audit@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kris Kennaway writes: > Hi all, > > It would be useful when someone commits a patch here to follow up the > original message with a note stating as such, otherwise it's hard to > tell whether the patch is outstanding. Most of the recent patches by > Mike Barcroft seem to be in this category. Are there any outstanding? > > Kris It's also sort of a problem for me, as I have to go through cvs logs to see when my stuff was committed. I keep all my uncommitted patches available at: http://testbed.q9media.net/freebsd/ Dig this idea. Have CVS read the 'Submitted by:' line and send the submitter a copy of the commit log message sent to -cvs-all. Since someone sending a patch will likely have some idea what CVS is, they won't be too confused by receiving a commit log. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-audit" in the body of the message