public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] generating ChangeLog files automatically from `cvs commit`
Date: Wed, 17 Aug 2005 15:28:46 +0200	[thread overview]
Message-ID: <200508171528.47231@enterprise.flameeyes.is-a-geek.org> (raw)
In-Reply-To: <43033831.4030203@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]

On Wednesday 17 August 2005 15:14, Grobian wrote:
> The whole point was that I like avoiding storing data double
> (redundant), if that can be done easily.
It has its own pro and cons as quite everything. You can avoid storing data 
double but makes more difficult to access it by the priority end users (devs; 
while users use changelogs, too, devs are the ones who really need to access 
them).

> As for the forum example: it wouldn't be a foreign key if there wasn't a
> left outer join to look up the respective value for the column.  And so
> that left outer join is here to generate the Changelog to be "backwards
> compatible"
The problem is where this is going to be generated. If this is going to be 
generated in the staging box before going in rsync, every dev that doesn't 
use rsync should use cvs log command to get the data, and this is quite 
unpractical (and requires bandwidth and adds load to the cvs server).

So we should balance redundancy and load... I still think that a little 
redundancy of the changelogs saves us from having to add load to the staging 
or cvs box...

-- 
Diego "Flameeyes" Pettenò
Gentoo Developer - http://dev.gentoo.org/~flameeyes/
(Gentoo/FreeBSD, Video, Gentoo/AMD64, Sound, PAM)

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-08-17 13:32 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 22:18 [gentoo-dev] generating ChangeLog files automatically from `cvs commit` Mike Frysinger
2005-08-16 22:32 ` Kito
2005-08-16 23:03 ` Robin H. Johnson
2005-08-16 23:18   ` Mike Frysinger
2005-08-16 23:38     ` Ciaran McCreesh
2005-08-17  1:46       ` Jason Stubbs
2005-08-17  1:52         ` Ciaran McCreesh
2005-08-17  2:05           ` Mike Frysinger
2005-08-17 23:39         ` Aron Griffis
2005-08-18  0:09           ` Jason Stubbs
2005-08-18  0:13             ` Donnie Berkholz
2005-08-18  0:50               ` Mike Frysinger
2005-08-18 10:56               ` Jason Stubbs
2005-08-18  1:13             ` Aron Griffis
2005-08-17  3:46       ` Dice R. Random
2005-08-16 23:41 ` Michael Kohl
2005-08-17  0:29 ` Jeremy Huddleston
2005-08-17  1:03   ` Alec Warner
2005-08-17  1:13     ` Ciaran McCreesh
2005-08-17  1:44 ` Jason Stubbs
2005-08-17 12:16 ` Henrik Brix Andersen
2005-08-17 12:35   ` Diego 'Flameeyes' Pettenò
2005-08-17 12:36   ` Grobian
2005-08-17 12:45     ` Henrik Brix Andersen
2005-08-17 12:57     ` Diego 'Flameeyes' Pettenò
2005-08-17 13:14       ` Grobian
2005-08-17 13:28         ` Diego 'Flameeyes' Pettenò [this message]
2005-08-17 13:04   ` Mike Frysinger
2005-08-17 13:45     ` Henrik Brix Andersen
2005-08-17 20:02       ` Jon Portnoy
2005-08-17 20:09         ` warnera6
2005-08-17 22:15         ` Aaron Walker
2005-08-22  6:12 ` Andreas Vinsander

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=200508171528.47231@enterprise.flameeyes.is-a-geek.org \
    --to=flameeyes@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