> Depends on the size of the commit. For years there
> have been filters setup to avoid overwhelming the list
> w/ megacommits. Read the list archives for more
> details.
Thanks for explanation. However, five smaller commits lead to higher
traffic than one big... There is also a risk that someone
Depends on the size of the commit. For years there
have been filters setup to avoid overwhelming the list
w/ megacommits. Read the list archives for more
details.
--- Jakub Vrana <[EMAIL PROTECTED]> wrote:
> It seems that some CVS commits to phpdoc isn't send
> to phpdoc list
> even if they are su
It seems that some CVS commits to phpdoc isn't send to phpdoc list
even if they are successful. I committed half an hour ago and the
notification still isn't in the list.
CVS told me "Mailing the commit email to [EMAIL PROTECTED]".
Sometimes it happens...
Goba
> > It's also not a solution for those Windows guys
>
> Huh? Those were Hamster rules, of course :) I'm on Windows, too, you
> know :)
Heh ;) I'll look at that Hamster... ;))
Goba
Gabor Hojtsy wrote:
> It's also not a solution for those Windows guys
Huh? Those were Hamster rules, of course :) I'm on Windows, too, you
know :)
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpOpenTracker.de/
Did I help you? Consider a gift: http://wis
> > > I think its better to split in phpdoc-de phpdoc-nl phpdoc-jp etc.
> > > I absolutely not interesteted in japanese commits, I even can't
> > > understand them. This applys do most other languages ;)
> >
> > =kill() Subject: "[PHP-DOC] cvs: phpdoc-ar"
> > =kill() Subject: "[PHP-DOC] cvs:
> One of the language maintainers use a local CVS server, and
> some automated CVS update script. It updates files one by one
> for some reason :((
Yes, our script uploads files one by one. We will see if we can do something
about it.
I remember there was a proposition for splitting mailing list
> Would phpdoc committers please remember that they don't need to commit
each
> file in cvs seperately, and it's usually only wise to do so if you wish to
> log very specific different notices, or they are in vastly different parts
> of the cvs repository.
>
> eg, you could do this:
>
> cd /your/s
On Tue, 19 Jun 2001, Jeroen van Wolffelaar wrote:
> Hello,
>
> Is it possible to back-populate this ML with the CVS commits during the
> downtime of toye.php.net?
> Or otherwise it might be a good idea to post the diff of 24-05 till 19-06
> here?
cvs diff -D 2001-05-24
will do the job fine, and
