Gentoo Archives: gentoo-scm

From: "Robin H. Johnson" <robbat2@g.o>
To: gentoo-scm@l.g.o
Subject: Re: [gentoo-scm] Splitting gentoo-x86 repository for easier consumption
Date: Sat, 11 Apr 2009 18:14:55
Message-Id: 20090411T181035Z@curie.orbis-terrarum.net
In Reply to: Re: [gentoo-scm] Splitting gentoo-x86 repository for easier consumption by Caleb Cushing
On Sat, Apr 11, 2009 at 02:05:56PM -0400, Caleb Cushing wrote:
> On Sat, Apr 11, 2009 at 1:29 PM, Robin H. Johnson <robbat2@g.o> wrote: > > He already included the slim Manifests in his list of items. > I'm talking about 'history' not new stuff. I'm talking about writing > them out of whatever is in cvs now. (I assume they are in cvs...)
Ah, yes, we could possibly exclude all lines other than DIST during the conversion. It would mean post-processing is needed to use the tree anyway, but that shouldn't be a problem.
> > This one will not come to pass I think. The CVS commit message is NOT > > the same as the ChangeLog entry. The ChangeLog entry is for user > > consumption, the commit message is for developers. > if we moved away from rsync neither would be necessary.
We're still going to be offering rsync to users. The entire point was to have the ability to have different messages for different destinations. I very seldom read ChangeLog directly, but I do read commit messages via the commits mailing list. To give a better example, I'd like to bring up the MogileFS SVN repo over at Danga. There is a CHANGES file, and it contains ONLY user-visible changes, it's short and easy to read. The commit messages on the other hand are longer and often include the reason behind some of the changes, and various notes on the commit. There is always a commit message, but only sometimes is there a CHANGES entry. -- Robin Hugh Johnson Gentoo Linux Developer & Infra Guy E-Mail : robbat2@g.o GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85

Replies

Subject Author
Re: [gentoo-scm] Splitting gentoo-x86 repository for easier consumption Caleb Cushing <xenoterracide@×××××.com>