From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Thomas Lord Newsgroups: gmane.emacs.devel Subject: Re: MAINTAINERS file Date: Thu, 06 Mar 2008 13:21:31 -0800 Message-ID: <47D0605B.6070505@emf.net> References: <18375.18663.981150.252393@kahikatea.snap.net.nz> <87od9wt19m.fsf@elegiac.orebokech.com> <87tzjnvjhc.fsf@red-bean.com> <87ablffdf7.fsf@catnip.gol.com> <4s4pbm9lrb.fsf@fencepost.gnu.org> <87skz4n6lu.fsf@catnip.gol.com> <87r6enpy30.fsf@catnip.gol.com> <47D050B0.1060608@emf.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------000901060208090506060108" X-Trace: ger.gmane.org 1204832666 4020 80.91.229.12 (6 Mar 2008 19:44:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 6 Mar 2008 19:44:26 +0000 (UTC) Cc: Glenn Morris , rms@gnu.org, lekktu@gmail.com, emacs-devel@gnu.org, kfogel@red-bean.com, Stefan Monnier , paul.r.ml@gmail.com, Miles Bader To: Thomas Lord Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Mar 06 20:44:43 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JXM14-00024G-Bm for ged-emacs-devel@m.gmane.org; Thu, 06 Mar 2008 20:44:34 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JXM0W-000394-Pk for ged-emacs-devel@m.gmane.org; Thu, 06 Mar 2008 14:44:00 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JXM0S-00036n-04 for emacs-devel@gnu.org; Thu, 06 Mar 2008 14:43:56 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JXM0R-00035v-FU for emacs-devel@gnu.org; Thu, 06 Mar 2008 14:43:55 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JXM0R-00035k-9f for emacs-devel@gnu.org; Thu, 06 Mar 2008 14:43:55 -0500 Original-Received: from mail.42inc.com ([205.149.0.25]) by monty-python.gnu.org with esmtps (SSL 3.0:RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1JXM0G-0003wr-1b; Thu, 06 Mar 2008 14:43:44 -0500 X-TFF-CGPSA-Version: 1.5 X-TFF-CGPSA-Filter-42inc: Scanned X-42-Virus-Scanned: by 42 Antivirus -- Found to be clean. Original-Received: from [69.236.65.4] (account lord@emf.net HELO [192.168.1.64]) by mail.42inc.com (CommuniGate Pro SMTP 5.0.13) with ESMTPA id 24715966; Thu, 06 Mar 2008 11:43:29 -0800 User-Agent: Thunderbird 1.5.0.5 (X11/20060808) In-Reply-To: <47D050B0.1060608@emf.net> X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:91542 Archived-At: This is a multi-part message in MIME format. --------------000901060208090506060108 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Thomas Lord wrote: > The "zen" of Arch is that each commit > should represent a kind of "complete thought" so that the record of > changesets is a kind of documentation of the logical steps that were > taken in the evolution of a branch. Maybe someone should create a blog host where blog posts are automatically generated from Arch (or bzr, whatever) commit messages (with links to the patch and to the source tree for the revision). That should be pretty easy to do and might a convenient "browser" for branches that are central to the project. -t --------------000901060208090506060108 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Thomas Lord wrote:
The "zen" of Arch is that each commit
should represent a kind of "complete thought" so that the record of
changesets is a kind of documentation of the logical steps that were
taken in the evolution of a branch.


Maybe someone should create a blog host where blog
posts are automatically generated from Arch (or bzr, whatever)
commit messages (with links to the patch and to the source tree
for the revision).   That should be pretty easy to do and might
a convenient "browser" for branches that are central to the project.

-t


--------------000901060208090506060108--