Mike Frysinger wrote:
> suggestion:
> stop keeping ChangeLog files in CVS and instead, let them be generated
> automagically by the cvs server using the last 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 prefix
On Thursday 18 August 2005 09:13, 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
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 o
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
-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 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 o
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
tools. This is similar to when I changed ekeyword to sort KE
-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
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. :)
You are the weakest link, goodbye!
--
gentoo-dev@gentoo.org mailing list
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. :)
--
Jon Portnoy
avenj/irc.freenode.net
--
gentoo-dev@gentoo.org mailing list
On Wed, 2005-08-17 at 09:04 -0400, Mike Frysinger wrote:
> it was part joke and part seriousness ... i already have my commits scripted
> with echangelog/repoman, but that isnt the point
Ok - a bit hard to tell that you were joking there...
> i delete one version for being old, stabilize another
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 pa
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 u
Ok. I'll elaborate some. I was not planning to do so, but it appears
there is some misinterpretation here. It was not my intention to let
you all know that I think cvs and Changelogs are databases. They most
certainly are, but that is not the point here, and may be saved for
another discuss
On Wednesday 17 August 2005 14:36, Grobian wrote:
> From a database point of view, it is evil to duplicate values in an
> automated manner, just use a foreign key for such purposes. In other
> words, avoid duplication. If such bash function is a common tool then
> -- apart from wondering why it
On Wed, 2005-08-17 at 14:36 +0200, Grobian wrote:
> From a database point of view, it is evil to duplicate values in an
> automated manner, just use a foreign key for such purposes. In other
> words, avoid duplication. If such bash function is a common tool then
> -- apart from wondering why
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, it
On Wednesday 17 August 2005 14:16, Henrik Brix Andersen wrote:
> Can you give an example of why you would want to use different commit
> messages in a single commit?
By the way, repoman commit doesn't allow you to do so: as it commits "in
block" and you must call it also to change a single file in
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 of commit
> messages. if you really want to keep a commit message out of the changelog,
> then we com
On 8/16/05, Ciaran McCreesh <[EMAIL PROTECTED]> wrote:
> GLEP 31 is withdrawn until Gentoo gets some means of removing commit
> access from people who say "nyah nyah I don't feel like following the
> rules and so I'll just carry on breaking stuff as I see fit". As it
> stands I've been told by vari
On Tuesday 16 August 2005 09:52 pm, Ciaran McCreesh wrote:
> On Wed, 17 Aug 2005 10:46:23 +0900 Jason Stubbs <[EMAIL PROTECTED]>
>
> wrote:
> | On Wednesday 17 August 2005 08:38, Ciaran McCreesh wrote:
> | > GLEP 31 is withdrawn until Gentoo gets some means of removing commit
> | > access from peop
On Wed, 17 Aug 2005 10:46:23 +0900 Jason Stubbs <[EMAIL PROTECTED]>
wrote:
| On Wednesday 17 August 2005 08:38, Ciaran McCreesh wrote:
| > GLEP 31 is withdrawn until Gentoo gets some means of removing commit
| > access from people who say "nyah nyah I don't feel like following
| > the rules and so
On Wednesday 17 August 2005 08:38, Ciaran McCreesh wrote:
> GLEP 31 is withdrawn until Gentoo gets some means of removing commit
> access from people who say "nyah nyah I don't feel like following the
> rules and so I'll just carry on breaking stuff as I see fit". As it
> stands I've been told by v
On Wednesday 17 August 2005 07:18, Mike Frysinger wrote:
> suggestion:
> stop keeping ChangeLog files in CVS and instead, let them be generated
> automagically by the cvs server using the last of
> commit messages.
You stole my idea! I guess I better ack it then. ;)
--
Jason Stubbs
pgpkxElZpa
On Tue, 16 Aug 2005 21:03:21 -0400 Alec Warner <[EMAIL PROTECTED]>
wrote:
| Also forcing a Changelog syntax makes portage's -l feature useful,
| since it attempts to parse the Changelog to provide sane
| entries...but some Changelogs don't seem to be in the correct syntax
| that the -l functionalit
-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 of commit
>>messages. if
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 of commit
> messages. if you really want to keep a commit message out of the changelog,
> then we com
Mike Frysinger wrote:
> suggestion:
> stop keeping ChangeLog files in CVS and instead, let them be generated
> automagically by the cvs server using the last of commit
> messages.
As I already use a bash function called ecommit which writes a ChangeLog
entry before it runs repoman and finall
On Tue, 16 Aug 2005 19:18:21 -0400 Mike Frysinger <[EMAIL PROTECTED]>
wrote:
| On Tuesday 16 August 2005 07:03 pm, Robin H. Johnson wrote:
| > On Tue, Aug 16, 2005 at 06:18:29PM -0400, Mike Frysinger wrote:
| > > logic:
| > Question:
| > - are CVS commit messages UTF8 safe?
|
| GLEP 31 came to min
On Tuesday 16 August 2005 07:03 pm, Robin H. Johnson wrote:
> On Tue, Aug 16, 2005 at 06:18:29PM -0400, Mike Frysinger wrote:
> > logic:
> Question:
> - are CVS commit messages UTF8 safe?
GLEP 31 came to mind when i was writing the e-mail but i forgot to mention
it ... maybe ciaran can hop in her
On Tue, Aug 16, 2005 at 06:18:29PM -0400, Mike Frysinger wrote:
> stop keeping ChangeLog files in CVS and instead, let them be generated
> automagically by the cvs server using the last of commit
> messages. if you really want to keep a commit message out of the changelog,
> then we come up wi
On Aug 16, 2005, at 5:18 PM, Mike Frysinger wrote:
logic:
- i'm lazy
- i hate typing the samething twice (yes, bash scripting with
echangelog can
kind of take care of this) ... it doesnt handle if you want to use
different
commit messages for different files
- shrinks ChangeLog size fo
suggestion:
stop keeping ChangeLog files in CVS and instead, let them be generated
automagically by the cvs server using the last 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 with a period
(
33 matches
Mail list logo
