You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs-cvs@perl.apache.org by go...@apache.org on 2004/11/17 22:46:05 UTC
svn commit: rev 76176 - in perl/modperl/docs/trunk: bin src
Author: gozer
Date: Wed Nov 17 13:46:03 2004
New Revision: 76176
Modified:
perl/modperl/docs/trunk/bin/site_build
perl/modperl/docs/trunk/src/config.cfg
Log:
Parts of the move from CVS to subversion. Start generating the
site from svn.
Modified: perl/modperl/docs/trunk/bin/site_build
==============================================================================
--- perl/modperl/docs/trunk/bin/site_build (original)
+++ perl/modperl/docs/trunk/bin/site_build Wed Nov 17 13:46:03 2004
@@ -54,7 +54,7 @@
$flags .= 'v' if $name =~ /verbose/;
$flags = $flags ? "-$flags" : "";
- system("cvs up -dP >/dev/null 2>&1");
+ system("svn update >/dev/null 2>&1");
system("bin/build $flags");
Modified: perl/modperl/docs/trunk/src/config.cfg
==============================================================================
--- perl/modperl/docs/trunk/src/config.cfg (original)
+++ perl/modperl/docs/trunk/src/config.cfg Wed Nov 17 13:46:03 2004
@@ -75,7 +75,7 @@
)],
copy_skip => [
- '(?:^|\/)CVS(?:\/|$)', # skip cvs control files
+ '(?:^|\/)\.svn(?:\/|$)', # skip svn control files
'#|~', # skip emacs backup files
],
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-cvs-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-cvs-help@perl.apache.org
Re: please post a summary of infrastructure changes
Posted by Stas Bekman <st...@stason.org>.
Garrett Rooney wrote:
> Stas Bekman wrote:
>
>> Garrett Rooney wrote:
>
>
>>> For what it's worth the APR seems to have settled on using
>>> commits@apr.apache.org.
>>
>>
>>
>> But we need to differentiate between docs and code commits since the
>> two go to different lists. Otherwise it's a good idea.
>
>
> commits@ and commits-docs@ (or docs-commits@ I guess, I don't have a
> strong opinion one way or the other)
fine with me. and no changes is fine with me too.
> or just send them both to the same
> list, that's what httpd seems to do.
thanks, but we aren't not httpd.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: please post a summary of infrastructure changes
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
Stas Bekman wrote:
> Garrett Rooney wrote:
>> For what it's worth the APR seems to have settled on using
>> commits@apr.apache.org.
>
>
> But we need to differentiate between docs and code commits since the two
> go to different lists. Otherwise it's a good idea.
commits@ and commits-docs@ (or docs-commits@ I guess, I don't have a
strong opinion one way or the other) or just send them both to the same
list, that's what httpd seems to do.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: please post a summary of infrastructure changes
Posted by Stas Bekman <st...@stason.org>.
Garrett Rooney wrote:
> Stas Bekman wrote:
>
>> There aren't only difs, so -changes make more sense. Assuming that we
>> don't move to some kps or uqz version system any time soon, -svn will
>> work too.
>>
>> May be it's the best to keep things unmodified. Changing the name will
>> require archive engines to adjust and those are usually slow to
>> followup. (However this is possible if aliases are kept)
>
>
> For what it's worth the APR seems to have settled on using
> commits@apr.apache.org.
But we need to differentiate between docs and code commits since the two
go to different lists. Otherwise it's a good idea.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: please post a summary of infrastructure changes
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
Stas Bekman wrote:
> There aren't only difs, so -changes make more sense. Assuming that we
> don't move to some kps or uqz version system any time soon, -svn will
> work too.
>
> May be it's the best to keep things unmodified. Changing the name will
> require archive engines to adjust and those are usually slow to
> followup. (However this is possible if aliases are kept)
For what it's worth the APR seems to have settled on using
commits@apr.apache.org.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: please post a summary of infrastructure changes
Posted by Stas Bekman <st...@stason.org>.
Philippe M. Chiasson wrote:
[...]
>>>> And if you are already changing the name of the list, why calling it
>>>> -cvs? call it -svn, no?
>>>
>>>
>>> Yeah, or -changes to be backend agnostic. But that would mean even
>>> more infrastructure changes
>>> on the other end, so at this point, I am just trying to keep it simple.
>>
>>
>> -changes is nice, but -cvs or -svn is shorter and maps nicer with -dev
>> :) but either way is fine with me.
>
> How about -diff then ?
There aren't only difs, so -changes make more sense. Assuming that we
don't move to some kps or uqz version system any time soon, -svn will work
too.
May be it's the best to keep things unmodified. Changing the name will
require archive engines to adjust and those are usually slow to followup.
(However this is possible if aliases are kept)
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: please post a summary of infrastructure changes
Posted by "Philippe M. Chiasson" <go...@ectoplasm.org>.
Stas Bekman wrote:
> Philippe M. Chiasson wrote:
>
>>> Please post a summary of infrastructure changes.
>>
>> Yes, I was planning on posting just that as soon as everything is
>> moved over and settled down. At this point
>> we are still in a flux-like state where even though the code is moved
>> over subversion, there are still a few things
>> that needs to be done on the infra side of things. I'll update the
>> list as things move forward.
>
> sure, take your time, sorry for rushing that. I would have just
> prefered to know what's planned ahead, in case some things might be
> inappropriate and better changed early.
Yeah, the whole migration process was done more or less chaotically as
we can all attest to ;-)
>>> For example this message was posted to docs-cvs which didn't exist
>>> before. It used to be modperl-docs-cvs, so mail filters now fail.
>>> One needs to update the mail info docs as well to reflect those
>>> changes. It also may affect archives.
>>
>> Yeah, that's strange, there were a lot of email aliases in there.
>> I'll get that fixed asap.
>
> I suppose that all aliases that aren't under @perl.apache.org could be
> dropped. It's been awhile since the move was done. But it's probably
> the best to layout a plan for the changes first if that makes sense.
Yes, let's start an extensive list of all our email addresses and see
what we can cleanup a bit. I'll start another thread for this.
>>> And if you are already changing the name of the list, why calling it
>>> -cvs? call it -svn, no?
>>
>> Yeah, or -changes to be backend agnostic. But that would mean even
>> more infrastructure changes
>> on the other end, so at this point, I am just trying to keep it simple.
>
> -changes is nice, but -cvs or -svn is shorter and maps nicer with -dev
> :) but either way is fine with me.
How about -diff then ?
--------------------------------------------------------------------------------
Philippe M. Chiasson m/gozer\@(apache|cpan|ectoplasm)\.org/ GPG KeyID : 88C3A5A5
http://gozer.ectoplasm.org/ F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3A5A5
Re: please post a summary of infrastructure changes
Posted by Stas Bekman <st...@stason.org>.
Philippe M. Chiasson wrote:
>> Please post a summary of infrastructure changes.
>
>
> Yes, I was planning on posting just that as soon as everything is moved
> over and settled down. At this point
> we are still in a flux-like state where even though the code is moved
> over subversion, there are still a few things
> that needs to be done on the infra side of things. I'll update the list
> as things move forward.
sure, take your time, sorry for rushing that. I would have just prefered
to know what's planned ahead, in case some things might be inappropriate
and better changed early.
>> For example this message was posted to docs-cvs which didn't exist
>> before. It used to be modperl-docs-cvs, so mail filters now fail. One
>> needs to update the mail info docs as well to reflect those changes.
>> It also may affect archives.
>
>
> Yeah, that's strange, there were a lot of email aliases in there. I'll
> get that fixed asap.
I suppose that all aliases that aren't under @perl.apache.org could be
dropped. It's been awhile since the move was done. But it's probably the
best to layout a plan for the changes first if that makes sense.
>> And if you are already changing the name of the list, why calling it
>> -cvs? call it -svn, no?
>
>
> Yeah, or -changes to be backend agnostic. But that would mean even more
> infrastructure changes
> on the other end, so at this point, I am just trying to keep it simple.
-changes is nice, but -cvs or -svn is shorter and maps nicer with -dev :)
but either way is fine with me.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: please post a summary of infrastructure changes
Posted by "Philippe M. Chiasson" <go...@ectoplasm.org>.
Stas Bekman wrote:
> gozer@apache.org wrote:
>
>> Author: gozer
>> Date: Wed Nov 17 13:46:03 2004
>> New Revision: 76176
>>
>> Modified:
>> perl/modperl/docs/trunk/bin/site_build
>> perl/modperl/docs/trunk/src/config.cfg
>> Log:
>> Parts of the move from CVS to subversion. Start generating the
>> site from svn.
>
>
> Please post a summary of infrastructure changes.
Yes, I was planning on posting just that as soon as everything is moved
over and settled down. At this point
we are still in a flux-like state where even though the code is moved
over subversion, there are still a few things
that needs to be done on the infra side of things. I'll update the list
as things move forward.
> For example this message was posted to docs-cvs which didn't exist
> before. It used to be modperl-docs-cvs, so mail filters now fail. One
> needs to update the mail info docs as well to reflect those changes.
> It also may affect archives.
Yeah, that's strange, there were a lot of email aliases in there. I'll
get that fixed asap.
> And if you are already changing the name of the list, why calling it
> -cvs? call it -svn, no?
Yeah, or -changes to be backend agnostic. But that would mean even more
infrastructure changes
on the other end, so at this point, I am just trying to keep it simple.
please post a summary of infrastructure changes
Posted by Stas Bekman <st...@stason.org>.
gozer@apache.org wrote:
> Author: gozer
> Date: Wed Nov 17 13:46:03 2004
> New Revision: 76176
>
> Modified:
> perl/modperl/docs/trunk/bin/site_build
> perl/modperl/docs/trunk/src/config.cfg
> Log:
> Parts of the move from CVS to subversion. Start generating the
> site from svn.
Please post a summary of infrastructure changes.
For example this message was posted to docs-cvs which didn't exist before.
It used to be modperl-docs-cvs, so mail filters now fail. One needs to
update the mail info docs as well to reflect those changes. It also may
affect archives.
And if you are already changing the name of the list, why calling it -cvs?
call it -svn, no?
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org