tests related patches

[Valery Masiutsin <va...@gmail.com>]

Hello.

Here is set of fresh patches.
Mostly this is fixes for tests directory - to make test running
against  apache2.
Fixes to apache2 module issues, that relate2  to multipart buffer processing.
Those ones sucked plenty of my blood to track them down, so they
deserved  better description. With request_req* in apache2 we can see
funny thing - names of structure fields are the same, but the filling
is rather different from what we have in apache1 , so it breakes
behaviour of boundary search functions - they are not able to detect
proper end of buffer. If you try to run upload.test without
multipart_buffer patch, you will get all headers past the end of the
file to your "uploaded" version. It is not easy to provide clean fix,
i mean libapreq2 is totally different library, comparing to version
rivet currently uses and import of it will require to do plenty of
changes, we just dont need.
Also i've done some changes to configure.ac, they should be obvious.
To apply patches please use  :
for file in ../*diff ; do patch -u -p1 < $file ; done
I am keeping my local copy in mercurial dvcs, and this is the default
format of patches it generates.

Regards Valery.

Re: tests related patches

[David Welton <da...@dedasys.com>]

> I checked Mercurial's website yesterday. There are some very interesting
> characteristics (like the non-existence of a central repository) and it's
> simple. It would be interesting in a small work group without the need
> of intense centralization. It wouldn't fit my needs though. I do need a
> central repository even for my personal projects.
>
> What do you guys think about Git? It was to me a recent discover
> that linux kernel switched from subversion to git.

I think I'll wait till things are sorted out amongst these different
systems.  Subversion works fine for me at the moment, and I don't see
much of a competitive advantage in utilizing one of the new systems
(darcs is another one).  When just one or two emerge as winners, then
maybe it'll be time to take a look.  I'd rather save my explorations
for other areas - like Google's Android.

Ciao,
-- 
David N. Welton

http://www.welton.it/davidw/

http://www.dedasys.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org

Re: tests related patches

[Massimo Manghi <ma...@unipr.it>]

Valery Masiutsin wrote:
> Hello, Massimo !
>
> Dont worry, i am quite happy with svn.
> But here are the important moments:
> 1. Mercurial has pretty good svn interaction set of tools - otherwise
> i would not be bothered.
> 2. Mercurial keeps all history locally  - it means i dont need
> internet connection to browse svn
>  history, or commit my local changes - which is probably most important for me.
> 3.Due to some constraints  - lack of time, lazyness, etc,  i  can have
>  periods of inactivity, which always ends up the same - i am spending
> much time going through  long "svn diff", trying to recall where did i
> finish, and what was actually finished. With mercurial i have a set of
> local commits, with their commit messages (which is invaluable).
> Think of  mercurial as about tool, which can simplify some things, not
> the svn replacement.
>
> Regards Valery.
>
>   
Thank you

I checked Mercurial's website yesterday. There are some very interesting
characteristics (like the non-existence of a central repository) and it's
simple. It would be interesting in a small work group without the need
of intense centralization. It wouldn't fit my needs though. I do need a
central repository even for my personal projects.

What do you guys think about Git? It was to me a recent discover
that linux kernel switched from subversion to git.

 -- Massimo


---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org

Re: tests related patches

[Valery Masiutsin <va...@gmail.com>]

Hello, Massimo !

Dont worry, i am quite happy with svn.
But here are the important moments:
1. Mercurial has pretty good svn interaction set of tools - otherwise
i would not be bothered.
2. Mercurial keeps all history locally  - it means i dont need
internet connection to browse svn
 history, or commit my local changes - which is probably most important for me.
3.Due to some constraints  - lack of time, lazyness, etc,  i  can have
 periods of inactivity, which always ends up the same - i am spending
much time going through  long "svn diff", trying to recall where did i
finish, and what was actually finished. With mercurial i have a set of
local commits, with their commit messages (which is invaluable).
Think of  mercurial as about tool, which can simplify some things, not
the svn replacement.

Regards Valery.

---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org

Re: tests related patches

[Massimo Manghi <ma...@unipr.it>]

Hi Valery

On Mon, 26 Nov 2007 15:53:55 +0200, Valery Masiutsin wrote
> Hello.
> 
> Here is set of fresh patches.
> Mostly this is fixes for tests directory - to make test running
> against  apache2.
> Fixes to apache2 module issues, that relate2  to multipart buffer processing.

unfortunately I won't be able to test them until friday. Busy week.

> [...]
> Also i've done some changes to configure.ac, they should be obvious.
> To apply patches please use  :
> for file in ../*diff ; do patch -u -p1 < $file ; done
> I am keeping my local copy in mercurial dvcs, and this is the default
> format of patches it generates.
> 

Another versioning system? There are too many of them around 
lately...

-- Massimo


---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org