> Tag CVS, move the python stuff however you like, leave the java stuff in
> and just ignore it. And we no longer need try to maintain compatibility
> with java gump in the metadata definitions.
>
> I suggest we clean up further when we move to SVN.
Ought we do these at the same time, just to g
Adam R. B. Jack wrote:
Thoughts?
Tag CVS, move the python stuff however you like, leave the java stuff in
and just ignore it. And we no longer need try to maintain compatibility
with java gump in the metadata definitions.
I suggest we clean up further when we move to SVN.
cheers,
- LSD
-
> Sorry for not understanding how nagging works, and perhaps the intent
already
> exists, but shouldn't a Gump instance have a "Concern Area", i.e. "Nag
> projects that have 'these' domains in the nag-address" ? And by default
only
> use the domain-name on the host it is running.
Nagging works for
On Friday 18 June 2004 23:30, Adam R. B. Jack wrote:
> Nagging is both a command line parameter (--notify) and has to be
> requested/enabled in the workspace (with reworked the code, I managed to default the former to be true, and ignore
> the second. :(
Sorry for not understanding how nagging w
rds,
Adam
- Original Message -
From: "Martin van den Bemt" <[EMAIL PROTECTED]>
To: "Gump code and data" <[EMAIL PROTECTED]>
Sent: Friday, June 18, 2004 12:45 PM
Subject: Re: Stray nags (was:Re: [VOTE RESULTS] Retire Java Gump)
> Just to prevent myself fro
Just to prevent myself from spamming when I set up gump on my "new" box
(running fc 2)..
Mvgr,
Martin
On Fri, 2004-06-18 at 17:30, Adam R. B. Jack wrote:
> > Is nagging on by default ?
> > If it is a config entry, it's probably best to have the nag only as a
> commandline parameter, to prevent "s
> How about a compromise? Here is my proposal:
>
> Fork the metadata tree (perhaps putting the new one in SVN) and make it
very clear that the gumpmeisters have no intention of maintaining the
traditional metadata themselves (but anyone with commit priviledges may
modify the traditional metadata i
Adam R. B. Jack wrote:
My problem is that suggestion of a -1 ... 'cos although we won't actually
stop folks running traditional Gumps, we aren't wanting to maintain two
metadata trees, we aren't wanting to maintain Traditional to work on current
metadata. Traditional will (with Jakarta Commons so M
> Is nagging on by default ?
> If it is a config entry, it's probably best to have the nag only as a
commandline parameter, to prevent "spam" in the future ?
Nagging is both a command line parameter (--notify) and has to be
requested/enabled in the workspace (with
On Fri, 2004-06-18 at 15:49, Adam R. B. Jack wrote:
> 'CleanUp' branch (perhaps move it to SVN) or something. There is significant
> risk/change w/ this branch (as stray nags have shown) and it'd be a good
> time to rework directories, etc.
Is nagging on by default ?
If it is a config entry, it's
It has been 10 days since the vote to retire Traditional Gump was put out.
As I read this [VOTE] mails on this list I see seven +1s (Leo, Adam,
Davanum, Martin, Nicola, Stefan, Stefano), one +0 (Michael), one -0 (the
suggestion of a -1 if traditional Gumps were stopped, Sebastian).
My problem is
11 matches
Mail list logo
