Mike Frysinger wrote:
suggestion:
stop keeping ChangeLog files in CVS and instead, let them be generated
automagically by the cvs server using the last arbitrary number of commit
messages. if you really want to keep a commit message out of the changelog,
then we come up with a simple
On Tue, 2005-08-16 at 18:18 -0400, Mike Frysinger wrote:
suggestion:
stop keeping ChangeLog files in CVS and instead, let them be generated
automagically by the cvs server using the last arbitrary number of commit
messages. if you really want to keep a commit message out of the changelog,
Extracted from what Henrik Brix Andersen wrote:
That's not a valid argument - you can use a bash function for calling
echangelog and repoman as shown numerous times on this list.
See my first answer (bash function).
See my first answer (bash function).
From a database point of view,
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
On Wednesday 17 August 2005 08:16 am, Henrik Brix Andersen wrote:
On Tue, 2005-08-16 at 18:18 -0400, Mike Frysinger wrote:
logic:
- i'm lazy
That's not a valid argument - you can use a bash function for calling
echangelog and repoman as shown numerous times on this list.
it was part joke
Jon Portnoy wrote:
On Wed, Aug 17, 2005 at 03:45:49PM +0200, Henrik Brix Andersen wrote:
not everyone uses echangelog
[snip]
it does, but not everyone uses echangelog
Why not?
Because I don't want to. :)
badjokeYou are the weakest link, goodbye!/badjoke
--
gentoo-dev@gentoo.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jon Portnoy wrote:
On Wed, Aug 17, 2005 at 03:45:49PM +0200, Henrik Brix Andersen wrote:
not everyone uses echangelog
[snip]
it does, but not everyone uses echangelog
Why not?
Because I don't want to. :)
I have no problem with people
On Thursday 18 August 2005 08:39, Aron Griffis wrote:
Jason Stubbs wrote: [Tue Aug 16 2005, 09:46:23PM EDT]
Repoman could check the commit message for being valid UTF-8 and
simply not allow the commit if it isn't. :)
Be careful, this steps over the line of creating policy by way of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Stubbs wrote:
| I don't quite get you here. GLEP 31 has been approved, no? That would
make
| it seem to me that the above suggestion is just making the QA tool help
| enforce existing policy. If there's a flaw in that line of thinking,
please
|
On Wednesday 17 August 2005 08:13 pm, Donnie Berkholz wrote:
Jason Stubbs wrote:
| I don't quite get you here. GLEP 31 has been approved, no? That would
make
| it seem to me that the above suggestion is just making the QA tool help
| enforce existing policy. If there's a flaw in that line of
Jason Stubbs wrote: [Wed Aug 17 2005, 08:09:39PM EDT]
I don't quite get you here. GLEP 31 has been approved, no? That
would make it seem to me that the above suggestion is just making
the QA tool help enforce existing policy. If there's a flaw in that
line of thinking, please point it out
suggestion:
stop keeping ChangeLog files in CVS and instead, let them be generated
automagically by the cvs server using the last arbitrary number of commit
messages. if you really want to keep a commit message out of the changelog,
then we come up with a simple policy of prefixing the message
On Tue, 2005-08-16 at 18:18 -0400, Mike Frysinger wrote:
suggestion:
stop keeping ChangeLog files in CVS and instead, let them be generated
automagically by the cvs server using the last arbitrary number of commit
messages. if you really want to keep a commit message out of the changelog,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Huddleston wrote:
On Tue, 2005-08-16 at 18:18 -0400, Mike Frysinger wrote:
suggestion:
stop keeping ChangeLog files in CVS and instead, let them be generated
automagically by the cvs server using the last arbitrary number of commit
14 matches
Mail list logo
