public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: package.mask
Date: Fri, 16 Jan 2009 12:10:47 +0300	[thread overview]
Message-ID: <1232097047.12190.2270.camel@localhost> (raw)
In-Reply-To: <20090115042441.GA556@hermes>

В Срд, 14/01/2009 в 20:24 -0800, Donnie Berkholz пишет:
> On 11:05 Mon 12 Jan     , AllenJB wrote:
> > In my opinion the cvs commit log and the ChangeLog serve 2 different  
> > purposes. The cvs log is for developers while the ChangeLog is for  
> > users. While the cvs log will likely just want to explain what change  
> > was made, the ChangeLog should explain why it was made.
> 
> So if you want to know both, you need to look in 2 places? That doesn't 
> seem very nice to me. 

We do not distribute portage tree trough cvs and rsync does not have
ChangeLog's. But even with cvs, cvs log is very slow ...

> Also in a distributed VCS, we'd want to generate 
> ChangeLogs from the commit logs

True. But portage tree is still CVS and until this happened we need
document all changes in ChangeLog's.

-- 
Peter.




  parent reply	other threads:[~2009-01-16  9:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1LLlaP-0002uA-VS@stork.gentoo.org>
2009-01-11  0:56 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: package.mask Friedrich Oslage
2009-01-11  9:31   ` Benedikt Böhm
2009-01-11  9:53     ` Ryan Hill
2009-01-12 10:42     ` Peter Volkov
2009-01-12 11:05       ` AllenJB
2009-01-12 17:20         ` Alec Warner
2009-01-15  4:24         ` Donnie Berkholz
2009-01-15 13:47           ` Maciej Mrozowski
2009-01-16  9:10           ` Peter Volkov [this message]
     [not found] <20130212124555.2BE272171D@flycatcher.gentoo.org>
2013-02-12 12:49 ` Markos Chandras
     [not found] <20120522081633.68EF32004B@flycatcher.gentoo.org>
2012-05-22  8:48 ` Samuli Suominen
2012-05-22  8:59   ` Michael Weber
     [not found] <20110617131002.8A61620054@flycatcher.gentoo.org>
2011-06-17 13:13 ` Samuli Suominen
     [not found] <E1Kkgs8-00036Q-6J@stork.gentoo.org>
2008-09-30 16:34 ` Alexis Ballier
     [not found] <E1K9RI1-0004c7-5K@stork.gentoo.org>
2008-06-21  6:43 ` Peter Volkov
2008-06-21  8:56   ` Albert Zeyer
2008-06-21 18:38     ` Robin H. Johnson
2008-06-22  0:57       ` Peter Weller
2008-06-22  9:57     ` Peter Volkov
2008-06-22 13:49       ` Alin Năstac
2008-06-22 14:41         ` Peter Weller
2008-06-23 18:15           ` Alec Warner
     [not found] <E1K5lqj-0000UP-Ph@stork.gentoo.org>
2008-06-10 10:38 ` Peter Volkov
     [not found] <E1K1kGr-00017l-53@stork.gentoo.org>
2008-05-30  5:34 ` Peter Volkov
     [not found] <E1Jxkak-0002zX-R9@stork.gentoo.org>
2008-05-18 15:51 ` Peter Volkov

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=1232097047.12190.2270.camel@localhost \
    --to=pva@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