[gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-02 Thread Duncan
Peter Volkov posted on Thu, 02 Jun 2011 09:09:04 +0400 as excerpted: One of the huge benefits in using git would be really fast emerge --syncs. Not having some kind of system for migrating users to git seems like a lot of the benefits are lost. Is git faster then rsync? I've never done any

Re: [gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-02 Thread Eray Aslan
On 2011-06-02 8:09 AM, Peter Volkov wrote: ChangeLog files are text to be distributed to our users so they are completely independent of vcs we use. Just ditch the Changelogs and be done with it. The only objection I know is that changelogs act as a NEWS file. Well, it is not a good enough

Re: [gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-02 Thread Nirbheek Chauhan
On Thu, Jun 2, 2011 at 4:59 AM, Jorge Manuel B. S. Vicetto jmbsvice...@gentoo.org wrote: On 01-06-2011 19:50, Nirbheek Chauhan wrote: The current situation is: (a) Not dire. (b) Not urgent. (c) has irked enough developers and users that people pushed council to update the policy about the

Re: [gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-02 Thread Ciaran McCreesh
On Thu, 2 Jun 2011 16:35:24 +0530 Nirbheek Chauhan nirbh...@gentoo.org wrote: (c) has irked enough developers and users that people pushed council to update the policy about the use of ChangeLogs. Yes, and I'm surprised that these same developers pushed towards a negative solution (kick

Re: [gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-02 Thread Patrick Lauer
On 06/02/11 09:40, Eray Aslan wrote: Is git faster then rsync? I've never done any checks but it'll be surprising if it will. Git usually is faster - except the initial clone. Basically, rsync protocol scales with the project size not with change size. We're discussing performance of

Re: [gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-02 Thread Jorge Manuel B. S. Vicetto
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01-06-2011 15:34, Ciaran McCreesh wrote: On Wed, 01 Jun 2011 18:27:04 +0300 Samuli Suominen ssuomi...@gentoo.org wrote: Wouldn't it be better to just trust devs to use common sense in what gets into ChangeLogs, and actually be grateful about if

Re: [gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-02 Thread Rich Freeman
On Thu, Jun 2, 2011 at 7:05 AM, Nirbheek Chauhan nirbh...@gentoo.org wrote: On Thu, Jun 2, 2011 at 4:59 AM, Jorge Manuel B. S. Vicetto jmbsvice...@gentoo.org wrote: (c) has irked enough developers and users that people pushed council to update the policy about the use of ChangeLogs. Yes,

[gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-01 Thread Markos Chandras
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 01/06/2011 04:08 μμ, Peter Volkov wrote: В Пнд, 30/05/2011 в 14:55 -0700, Brian Harring пишет: The problem is, that's a *fuzzy* definition. Ok, let's start with something and then we'll add more items if required. Currently I'd like to

Re: [gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-01 Thread Samuli Suominen
On 06/01/2011 06:15 PM, Markos Chandras wrote: On 01/06/2011 04:08 ¼¼, Peter Volkov wrote:  =4, 30/05/2011 2 14:55 -0700, Brian Harring ?8H5B: The problem is, that's a *fuzzy* definition. Ok, let's start with something and then we'll add more items if required. Currently I'd like to

Re: [gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-01 Thread Nathan Phillip Brink
On Wed, Jun 01, 2011 at 04:15:31PM +0100, Markos Chandras wrote: On 01/06/2011 04:08 , Peter Volkov wrote: ?? ??, 30/05/2011 ?? 14:55 -0700, Brian Harring ??: The problem is, that's a *fuzzy* definition. Ok, let's start with something and then we'll add more items if

Re: [gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-01 Thread Ciaran McCreesh
On Wed, 01 Jun 2011 18:27:04 +0300 Samuli Suominen ssuomi...@gentoo.org wrote: Wouldn't it be better to just trust devs to use common sense in what gets into ChangeLogs, and actually be grateful about if they take the time to sensor the crap out from it, and scrap the whole topic? This whole

Re: [gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-01 Thread Andreas K. Huettel
Am Mittwoch 01 Juni 2011, 17:27:04 schrieb Samuli Suominen: Wouldn't it be better to just trust devs to use common sense in what gets into ChangeLogs, and actually be grateful about if they take the time to sensor the crap out from it, and scrap the whole topic? The problem is, not everyone

Re: [gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-01 Thread Nirbheek Chauhan
On Wed, Jun 1, 2011 at 9:09 PM, Andreas K. Huettel dilfri...@gentoo.org wrote: Am Mittwoch 01 Juni 2011, 17:27:04 schrieb Samuli Suominen: Wouldn't it be better to just trust devs to use common sense in what gets into ChangeLogs, and actually be grateful about if they take the time to sensor

Re: [gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-01 Thread Andreas K. Huettel
So we come back to the problem being *CVS* not ChangeLog rules. Well of course we can just tell everyone go look it up on sources.gentoo.org. However, this is a different discussion. All this is such a massive waste of time. Can't we just expend this energy on the move to git? Ack, this is

[gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-01 Thread Duncan
Nathan Phillip Brink posted on Wed, 01 Jun 2011 11:30:21 -0400 as excerpted: On Wed, Jun 01, 2011 at 04:15:31PM +0100, Markos Chandras wrote: On 01/06/2011 04:08 , Peter Volkov wrote: ?? ??, 30/05/2011 ?? 14:55 -0700, Brian Harring ??: The problem is, that's a *fuzzy*

Re: [gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-01 Thread Nirbheek Chauhan
On Wed, Jun 1, 2011 at 9:54 PM, Andreas K. Huettel dilfri...@gentoo.org wrote: So we come back to the problem being *CVS* not ChangeLog rules. Well of course we can just tell everyone go look it up on sources.gentoo.org. However, this is a different discussion. sources.gentoo.org is a

Re: [gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-01 Thread Rich Freeman
On Wed, Jun 1, 2011 at 12:44 PM, Duncan 1i5t5.dun...@cox.net wrote: The current every change policy goes overboard, I doubt anyone disagrees, but it's worth repeating the point someone else made already, every added exception makes the rule harder to remember.  The four numbered exceptions

Re: [gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-01 Thread Dale
Rich Freeman wrote: I think that we need a simple policy like: Write up Changelogs for any change that impacts what gets installed on our user's computers. Then we can write up some guidelines about how to apply this policy in practice. I think the problem is that we're getting a bit

Re: [gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-01 Thread Jorge Manuel B. S. Vicetto
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01-06-2011 19:50, Nirbheek Chauhan wrote: On Wed, Jun 1, 2011 at 9:54 PM, Andreas K. Huettel dilfri...@gentoo.org wrote: So we come back to the problem being *CVS* not ChangeLog rules. Well of course we can just tell everyone go look it up

Re: [gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-01 Thread Matt Turner
On Wed, Jun 1, 2011 at 7:29 PM, Jorge Manuel B. S. Vicetto jmbsvice...@gentoo.org wrote: To be clear I support the goal to move our tree to git. However, I'd like to point out that simply moving to git will leave us in the same state. Assuming everyone agrees that git is far more useful than

Re: [gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-01 Thread Jorge Manuel B. S. Vicetto
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01-06-2011 22:59, Rich Freeman wrote: snip I think the problem is that we're getting a bit legalistic here. I have no idea why we even needed the policy change. IMHO what should happen is: 1. Dev does something significant and doesn't

Re: [gentoo-dev] Re: RFC: better policy for ChageLogs

2011-06-01 Thread Peter Volkov
В Срд, 01/06/2011 в 19:37 -0400, Matt Turner пишет: On Wed, Jun 1, 2011 at 7:29 PM, Jorge Manuel B. S. Vicetto jmbsvice...@gentoo.org wrote: To be clear I support the goal to move our tree to git. However, I'd like to point out that simply moving to git will leave us in the same state. ++