[AsteriskBrasil] [Fwd: [Asterisk-Announce] Asterisk project converts to Subversion version control system]
Fala Victor, tudo bem? Seguinte, baixei tudo pelo Yast.Será que é isso mesmo? Como ficaria, por exemplo para eu baixar o asterisk? Abraço Josué 2005/12/2, Victor Yure : > > Baixa o rpm de acordo com a versao do seu Suse. > > http://www.rpmfind.net/linux/rpm2html/search.php?query=subversion&submit=Search+...&system=&arch > = > > > []'s > > Victor. > > > 2005/12/2, Josué Conti : > > > Olá Victor, tudo bem? > > Como implemento isso no SUSE? > > > > Obrigado e um abraço > > > > Josué > > > > 2005/12/2, Victor Yure < victor.esmeraldo em gmail.com>: > > > olá, > > > > > > não tem. > > > > > > []'s > > > > > > 2005/12/2, Josué Conti : > > > > Diego, muito obrigado. Saberia dizer, se no SUSE já tem o > > subversion? > > > > > > > > Abraço > > > > > > > > Josué > > > > > > > > 2005/12/1, Diego Aguirre < dagmoller em yahoo.com.br>: > > > > > Josué, > > > > > > > > > > O subversion é bem parecido com o CVS... > > > > > > > > > > # svn checkout http://svn.digium.com/svn/asterisk/trunk asterisk > > > > > # svn checkout http://svn.digium.com/svn/zaptel/trunk zaptel > > > > > # svn checkout http://svn.digium.com/svn/libpri/trunk libpri > > > > > > > > > > para atualizar, segue o mesmo padrão do CVS... > > > > > > > > > > # svn update > > > > > > > > > > > > > > > OBS: é necessário ter o SubVersion instalado. não sei quanto as > > outras > > > > > distros, mas o Slackware 10.2 já vem com o subversion... > > > > > > > > > > > > > > > Sds, > > > > > > > > > > Diego Aguirre > > > > > Infodag - Informática > > > > > FWD#: 459696 > > > > > Nikotel#: 99 21 8138-2710 > > > > > EnumLookup#: +55 21 8138-2710 > > > > > DUNDi-br#: 21 8138-2710 > > > > > > > > > > Josué Conti escreveu: > > > > > > Diego, pelo CVS não se baixa mais nada do *? Tipo como fica > > agora, por exemplo? > > > > > > > > > > > > Abraço > > > > > > > > > > > > Josué > > > > > > > > > > > > 2005/12/1, Geraldo Fco. do Espírito Santo Jr. < > > geraldo.santo em gmail.com>: > > > > > > > > > > > >>alguem tem a receita de bola para usar o SVN para atualizar o *. > > > > > >> > > > > > >>[ ]s > > > > > >> > > > > > >>Geraldo > > > > > >> > > > > > >>2005/11/30, Diego Aguirre : > > > > > >> > > > > > >>>Pessoal, > > > > > >>> > > > > > >>>O repositório CVS do asterisk já era, agora é SubVersion... > > > > > >>> > > > > > >>> Mensagem Original > > > > > >>>Assunto: [Asterisk-Announce] Asterisk project converts to > > Subversion > > > > > >>>version control system > > > > > >>>Data: Mon, 28 Nov 2005 13:01:34 -0600 > > > > > >>>De: Asterisk Development Team < asteriskteam em digium.com> > > > > > >>>Para: asterisk-announce em arizona.digium.com > > > > > >>> > > > > > >>>The Asterisk development team is pleased to announce that we > > have > > > > > >>>migrated our project repositories and development processes > > over to the > > > > > >>>Subversion version control system! > > > > > >>> > > > > > >>>Effective immediately, the primary source code distribution > > point for > > > > > >>>Asterisk, Zaptel and other related projects (other than release > > tarballs > > > > > >>>of course) will be http://svn.digium.com. > > > > > >>> > > > > > >>>The actual SVN repositories are available at > > http://svn.digium.com/svn, > > > > > >>>and there is a ViewCVS web viewer available at > > > > > >>>http://svn.digium.com/view. There is a separate repository for > > each > > > > > >>>major project, and each repository is organized in the typical > > > > > >>>Subversion fashion... for example, the Asterisk repository is > > organized > > > > > >>>as follows: > > > > > >>> > > > > > >>> http://svn.digium.com/svn/asterisk/trunk (was CVS HEAD) > > > > > >>>http://svn.digium.com/svn/asterisk/branches/1.2 (was CVS v1-2) > > > > > >>> http://svn.digium.com/svn/asterisk/tags/1.2.0 (was CVS v1-2-0) > > > > > >>> > > > > > >>>Other branches and tags are named similarly. Builds of Asterisk > > made > > > > > >>>from the new repositories will report a 'show version' tag made > > of the > > > > > >>>SVN branch name and the repository revision number that was > > checked out > > > > > >>>(unlike the CVS 'show version' tags which incorporated the > > date/time of > > > > > >>>checkout). > > > > > >>> > > > > > >>>The 'asterisk-cvs' mailing list has been renamed to > > 'svn-commits' and > > > > > >>>will continue to receive commit messages for the all the major > > projects > > > > > >>>on our SVN server (existing subscriptions are still in effect). > > In > > > > > >>>addition, there are new project specific commit mailing lists > > as well: > > > > > >>> > > > > > >>> asterisk-commits > > > > > >>> asterisk-addons-commits > > > > > >>> zaptel-commits > > > > > >>> libpri-commits > > > > > >>> libiax2-commits > > > > > >>> > > > > > >>>All of these lists are available on lists.digium.com. > > Additionally, the > > > > > >>>commit messages will contain 'X-SVN-Author' and 'X-SVN-Branch' > > mail > > > > > >>>headers to allow you to sort/filter the commit messages in any >
[AsteriskBrasil] [Fwd: [Asterisk-Announce] Asterisk project converts to Subversion version control system]
Baixa o rpm de acordo com a versao do seu Suse. http://www.rpmfind.net/linux/rpm2html/search.php?query=subversion&submit=Search+...&system=&arch = []'s Victor. 2005/12/2, Josué Conti : > > Olá Victor, tudo bem? > Como implemento isso no SUSE? > > Obrigado e um abraço > > Josué > > 2005/12/2, Victor Yure : > > olá, > > > > não tem. > > > > []'s > > > > 2005/12/2, Josué Conti : > > > Diego, muito obrigado. Saberia dizer, se no SUSE já tem o subversion? > > > > > > Abraço > > > > > > Josué > > > > > > 2005/12/1, Diego Aguirre : > > > > Josué, > > > > > > > > O subversion é bem parecido com o CVS... > > > > > > > > # svn checkout http://svn.digium.com/svn/asterisk/trunk asterisk > > > > # svn checkout http://svn.digium.com/svn/zaptel/trunk zaptel > > > > # svn checkout http://svn.digium.com/svn/libpri/trunk libpri > > > > > > > > para atualizar, segue o mesmo padrão do CVS... > > > > > > > > # svn update > > > > > > > > > > > > OBS: é necessário ter o SubVersion instalado. não sei quanto as > outras > > > > distros, mas o Slackware 10.2 já vem com o subversion... > > > > > > > > > > > > Sds, > > > > > > > > Diego Aguirre > > > > Infodag - Informática > > > > FWD#: 459696 > > > > Nikotel#: 99 21 8138-2710 > > > > EnumLookup#: +55 21 8138-2710 > > > > DUNDi-br#: 21 8138-2710 > > > > > > > > Josué Conti escreveu: > > > > > Diego, pelo CVS não se baixa mais nada do *? Tipo como fica agora, > por exemplo? > > > > > > > > > > Abraço > > > > > > > > > > Josué > > > > > > > > > > 2005/12/1, Geraldo Fco. do Espírito Santo Jr. < > geraldo.santo em gmail.com>: > > > > > > > > > >>alguem tem a receita de bola para usar o SVN para atualizar o *. > > > > >> > > > > >>[ ]s > > > > >> > > > > >>Geraldo > > > > >> > > > > >>2005/11/30, Diego Aguirre : > > > > >> > > > > >>>Pessoal, > > > > >>> > > > > >>>O repositório CVS do asterisk já era, agora é SubVersion... > > > > >>> > > > > >>> Mensagem Original > > > > >>>Assunto: [Asterisk-Announce] Asterisk project converts to > Subversion > > > > >>>version control system > > > > >>>Data: Mon, 28 Nov 2005 13:01:34 -0600 > > > > >>>De: Asterisk Development Team > > > > >>>Para: asterisk-announce em arizona.digium.com > > > > >>> > > > > >>>The Asterisk development team is pleased to announce that we have > > > > >>>migrated our project repositories and development processes over > to the > > > > >>>Subversion version control system! > > > > >>> > > > > >>>Effective immediately, the primary source code distribution point > for > > > > >>>Asterisk, Zaptel and other related projects (other than release > tarballs > > > > >>>of course) will be http://svn.digium.com. > > > > >>> > > > > >>>The actual SVN repositories are available at > http://svn.digium.com/svn, > > > > >>>and there is a ViewCVS web viewer available at > > > > >>>http://svn.digium.com/view. There is a separate repository for > each > > > > >>>major project, and each repository is organized in the typical > > > > >>>Subversion fashion... for example, the Asterisk repository is > organized > > > > >>>as follows: > > > > >>> > > > > >>>http://svn.digium.com/svn/asterisk/trunk (was CVS HEAD) > > > > >>>http://svn.digium.com/svn/asterisk/branches/1.2 (was CVS v1-2) > > > > >>>http://svn.digium.com/svn/asterisk/tags/1.2.0 (was CVS v1-2-0) > > > > >>> > > > > >>>Other branches and tags are named similarly. Builds of Asterisk > made > > > > >>>from the new repositories will report a 'show version' tag made > of the > > > > >>>SVN branch name and the repository revision number that was > checked out > > > > >>>(unlike the CVS 'show version' tags which incorporated the > date/time of > > > > >>>checkout). > > > > >>> > > > > >>>The 'asterisk-cvs' mailing list has been renamed to 'svn-commits' > and > > > > >>>will continue to receive commit messages for the all the major > projects > > > > >>>on our SVN server (existing subscriptions are still in effect). > In > > > > >>>addition, there are new project specific commit mailing lists as > well: > > > > >>> > > > > >>> asterisk-commits > > > > >>> asterisk-addons-commits > > > > >>> zaptel-commits > > > > >>> libpri-commits > > > > >>> libiax2-commits > > > > >>> > > > > >>>All of these lists are available on lists.digium.com. > Additionally, the > > > > >>>commit messages will contain 'X-SVN-Author' and 'X-SVN-Branch' > mail > > > > >>>headers to allow you to sort/filter the commit messages in any > way you wish. > > > > >>> > > > > >>>One of the major benefits of this transition is that we will be > opening > > > > >>>up 'developer branches' for Asterisk Development Team members to > be able > > > > >>>to work on projects and make them available for public review, > testing > > > > >>>and participation; look for another announcement later this week > when > > > > >>>that process is ready. > > > > >>> > > > > >>>For the near future, we will continue to provide access to source > code > > > > >>>via CVS using the same servers/paths that you have previous
[AsteriskBrasil] [Fwd: [Asterisk-Announce] Asterisk project converts to Subversion version control system]
Olá Victor, tudo bem? Como implemento isso no SUSE? Obrigado e um abraço Josué 2005/12/2, Victor Yure : > olá, > > não tem. > > []'s > > 2005/12/2, Josué Conti : > > Diego, muito obrigado. Saberia dizer, se no SUSE já tem o subversion? > > > > Abraço > > > > Josué > > > > 2005/12/1, Diego Aguirre : > > > Josué, > > > > > > O subversion é bem parecido com o CVS... > > > > > > # svn checkout http://svn.digium.com/svn/asterisk/trunk asterisk > > > # svn checkout http://svn.digium.com/svn/zaptel/trunk zaptel > > > # svn checkout http://svn.digium.com/svn/libpri/trunk libpri > > > > > > para atualizar, segue o mesmo padrão do CVS... > > > > > > # svn update > > > > > > > > > OBS: é necessário ter o SubVersion instalado. não sei quanto as outras > > > distros, mas o Slackware 10.2 já vem com o subversion... > > > > > > > > > Sds, > > > > > > Diego Aguirre > > > Infodag - Informática > > > FWD#: 459696 > > > Nikotel#: 99 21 8138-2710 > > > EnumLookup#: +55 21 8138-2710 > > > DUNDi-br#: 21 8138-2710 > > > > > > Josué Conti escreveu: > > > > Diego, pelo CVS não se baixa mais nada do *? Tipo como fica agora, por > > > > exemplo? > > > > > > > > Abraço > > > > > > > > Josué > > > > > > > > 2005/12/1, Geraldo Fco. do Espírito Santo Jr. > > > gmail.com>: > > > > > > > >>alguem tem a receita de bola para usar o SVN para atualizar o *. > > > >> > > > >>[ ]s > > > >> > > > >>Geraldo > > > >> > > > >>2005/11/30, Diego Aguirre : > > > >> > > > >>>Pessoal, > > > >>> > > > >>>O repositório CVS do asterisk já era, agora é SubVersion... > > > >>> > > > >>> Mensagem Original > > > >>>Assunto: [Asterisk-Announce] Asterisk project converts to Subversion > > > >>>version control system > > > >>>Data: Mon, 28 Nov 2005 13:01:34 -0600 > > > >>>De: Asterisk Development Team > > > >>>Para: asterisk-announce em arizona.digium.com > > > >>> > > > >>>The Asterisk development team is pleased to announce that we have > > > >>>migrated our project repositories and development processes over to the > > > >>>Subversion version control system! > > > >>> > > > >>>Effective immediately, the primary source code distribution point for > > > >>>Asterisk, Zaptel and other related projects (other than release > > > >>>tarballs > > > >>>of course) will be http://svn.digium.com. > > > >>> > > > >>>The actual SVN repositories are available at http://svn.digium.com/svn, > > > >>>and there is a ViewCVS web viewer available at > > > >>>http://svn.digium.com/view. There is a separate repository for each > > > >>>major project, and each repository is organized in the typical > > > >>>Subversion fashion... for example, the Asterisk repository is organized > > > >>>as follows: > > > >>> > > > >>>http://svn.digium.com/svn/asterisk/trunk (was CVS HEAD) > > > >>>http://svn.digium.com/svn/asterisk/branches/1.2 (was CVS v1-2) > > > >>>http://svn.digium.com/svn/asterisk/tags/1.2.0 (was CVS v1-2-0) > > > >>> > > > >>>Other branches and tags are named similarly. Builds of Asterisk made > > > >>>from the new repositories will report a 'show version' tag made of the > > > >>>SVN branch name and the repository revision number that was checked out > > > >>>(unlike the CVS 'show version' tags which incorporated the date/time of > > > >>>checkout). > > > >>> > > > >>>The 'asterisk-cvs' mailing list has been renamed to 'svn-commits' and > > > >>>will continue to receive commit messages for the all the major projects > > > >>>on our SVN server (existing subscriptions are still in effect). In > > > >>>addition, there are new project specific commit mailing lists as well: > > > >>> > > > >>> asterisk-commits > > > >>> asterisk-addons-commits > > > >>> zaptel-commits > > > >>> libpri-commits > > > >>> libiax2-commits > > > >>> > > > >>>All of these lists are available on lists.digium.com. Additionally, the > > > >>>commit messages will contain 'X-SVN-Author' and 'X-SVN-Branch' mail > > > >>>headers to allow you to sort/filter the commit messages in any way you > > > >>>wish. > > > >>> > > > >>>One of the major benefits of this transition is that we will be opening > > > >>>up 'developer branches' for Asterisk Development Team members to be > > > >>>able > > > >>>to work on projects and make them available for public review, testing > > > >>>and participation; look for another announcement later this week when > > > >>>that process is ready. > > > >>> > > > >>>For the near future, we will continue to provide access to source code > > > >>>via CVS using the same servers/paths that you have previously been > > > >>>using; once every day, the relevant Subversion branches will be copied > > > >>>over into CVS and brought up to date. We expect to keep updating CVS > > > >>>HEAD this way for three to six months; the other branches will be > > > >>>maintained for six to nine months. However the CVS repositories will be > > > >>>updated in a single commit each day and will not contain any detailed > > > >>>revision history for the changes that are made. We en
[AsteriskBrasil] [Fwd: [Asterisk-Announce] Asterisk project converts to Subversion version control system]
olá, não tem. []'s 2005/12/2, Josué Conti : > Diego, muito obrigado. Saberia dizer, se no SUSE já tem o subversion? > > Abraço > > Josué > > 2005/12/1, Diego Aguirre : > > Josué, > > > > O subversion é bem parecido com o CVS... > > > > # svn checkout http://svn.digium.com/svn/asterisk/trunk asterisk > > # svn checkout http://svn.digium.com/svn/zaptel/trunk zaptel > > # svn checkout http://svn.digium.com/svn/libpri/trunk libpri > > > > para atualizar, segue o mesmo padrão do CVS... > > > > # svn update > > > > > > OBS: é necessário ter o SubVersion instalado. não sei quanto as outras > > distros, mas o Slackware 10.2 já vem com o subversion... > > > > > > Sds, > > > > Diego Aguirre > > Infodag - Informática > > FWD#: 459696 > > Nikotel#: 99 21 8138-2710 > > EnumLookup#: +55 21 8138-2710 > > DUNDi-br#: 21 8138-2710 > > > > Josué Conti escreveu: > > > Diego, pelo CVS não se baixa mais nada do *? Tipo como fica agora, por > > > exemplo? > > > > > > Abraço > > > > > > Josué > > > > > > 2005/12/1, Geraldo Fco. do Espírito Santo Jr. > > gmail.com>: > > > > > >>alguem tem a receita de bola para usar o SVN para atualizar o *. > > >> > > >>[ ]s > > >> > > >>Geraldo > > >> > > >>2005/11/30, Diego Aguirre : > > >> > > >>>Pessoal, > > >>> > > >>>O repositório CVS do asterisk já era, agora é SubVersion... > > >>> > > >>> Mensagem Original > > >>>Assunto: [Asterisk-Announce] Asterisk project converts to Subversion > > >>>version control system > > >>>Data: Mon, 28 Nov 2005 13:01:34 -0600 > > >>>De: Asterisk Development Team > > >>>Para: asterisk-announce em arizona.digium.com > > >>> > > >>>The Asterisk development team is pleased to announce that we have > > >>>migrated our project repositories and development processes over to the > > >>>Subversion version control system! > > >>> > > >>>Effective immediately, the primary source code distribution point for > > >>>Asterisk, Zaptel and other related projects (other than release tarballs > > >>>of course) will be http://svn.digium.com. > > >>> > > >>>The actual SVN repositories are available at http://svn.digium.com/svn, > > >>>and there is a ViewCVS web viewer available at > > >>>http://svn.digium.com/view. There is a separate repository for each > > >>>major project, and each repository is organized in the typical > > >>>Subversion fashion... for example, the Asterisk repository is organized > > >>>as follows: > > >>> > > >>>http://svn.digium.com/svn/asterisk/trunk (was CVS HEAD) > > >>>http://svn.digium.com/svn/asterisk/branches/1.2 (was CVS v1-2) > > >>>http://svn.digium.com/svn/asterisk/tags/1.2.0 (was CVS v1-2-0) > > >>> > > >>>Other branches and tags are named similarly. Builds of Asterisk made > > >>>from the new repositories will report a 'show version' tag made of the > > >>>SVN branch name and the repository revision number that was checked out > > >>>(unlike the CVS 'show version' tags which incorporated the date/time of > > >>>checkout). > > >>> > > >>>The 'asterisk-cvs' mailing list has been renamed to 'svn-commits' and > > >>>will continue to receive commit messages for the all the major projects > > >>>on our SVN server (existing subscriptions are still in effect). In > > >>>addition, there are new project specific commit mailing lists as well: > > >>> > > >>> asterisk-commits > > >>> asterisk-addons-commits > > >>> zaptel-commits > > >>> libpri-commits > > >>> libiax2-commits > > >>> > > >>>All of these lists are available on lists.digium.com. Additionally, the > > >>>commit messages will contain 'X-SVN-Author' and 'X-SVN-Branch' mail > > >>>headers to allow you to sort/filter the commit messages in any way you > > >>>wish. > > >>> > > >>>One of the major benefits of this transition is that we will be opening > > >>>up 'developer branches' for Asterisk Development Team members to be able > > >>>to work on projects and make them available for public review, testing > > >>>and participation; look for another announcement later this week when > > >>>that process is ready. > > >>> > > >>>For the near future, we will continue to provide access to source code > > >>>via CVS using the same servers/paths that you have previously been > > >>>using; once every day, the relevant Subversion branches will be copied > > >>>over into CVS and brought up to date. We expect to keep updating CVS > > >>>HEAD this way for three to six months; the other branches will be > > >>>maintained for six to nine months. However the CVS repositories will be > > >>>updated in a single commit each day and will not contain any detailed > > >>>revision history for the changes that are made. We encourage all users > > >>>to transition to using Subversion for tracking development as soon as > > >>>possible. > > >>> > > >>>(Special thanks to chipig, sussman, darix, jerenkrantz, eh, mbk and the > > >>>others on #svn-dev who helped solve some sticky issues on Saturday > > >>>evening of Thanksgiving weekend ) > > >>> > > >>>_
[AsteriskBrasil] [Fwd: [Asterisk-Announce] Asterisk project converts to Subversion version control system]
Diego, muito obrigado. Saberia dizer, se no SUSE já tem o subversion? Abraço Josué 2005/12/1, Diego Aguirre : > Josué, > > O subversion é bem parecido com o CVS... > > # svn checkout http://svn.digium.com/svn/asterisk/trunk asterisk > # svn checkout http://svn.digium.com/svn/zaptel/trunk zaptel > # svn checkout http://svn.digium.com/svn/libpri/trunk libpri > > para atualizar, segue o mesmo padrão do CVS... > > # svn update > > > OBS: é necessário ter o SubVersion instalado. não sei quanto as outras > distros, mas o Slackware 10.2 já vem com o subversion... > > > Sds, > > Diego Aguirre > Infodag - Informática > FWD#: 459696 > Nikotel#: 99 21 8138-2710 > EnumLookup#: +55 21 8138-2710 > DUNDi-br#: 21 8138-2710 > > Josué Conti escreveu: > > Diego, pelo CVS não se baixa mais nada do *? Tipo como fica agora, por > > exemplo? > > > > Abraço > > > > Josué > > > > 2005/12/1, Geraldo Fco. do Espírito Santo Jr. : > > > >>alguem tem a receita de bola para usar o SVN para atualizar o *. > >> > >>[ ]s > >> > >>Geraldo > >> > >>2005/11/30, Diego Aguirre : > >> > >>>Pessoal, > >>> > >>>O repositório CVS do asterisk já era, agora é SubVersion... > >>> > >>> Mensagem Original > >>>Assunto: [Asterisk-Announce] Asterisk project converts to Subversion > >>>version control system > >>>Data: Mon, 28 Nov 2005 13:01:34 -0600 > >>>De: Asterisk Development Team > >>>Para: asterisk-announce em arizona.digium.com > >>> > >>>The Asterisk development team is pleased to announce that we have > >>>migrated our project repositories and development processes over to the > >>>Subversion version control system! > >>> > >>>Effective immediately, the primary source code distribution point for > >>>Asterisk, Zaptel and other related projects (other than release tarballs > >>>of course) will be http://svn.digium.com. > >>> > >>>The actual SVN repositories are available at http://svn.digium.com/svn, > >>>and there is a ViewCVS web viewer available at > >>>http://svn.digium.com/view. There is a separate repository for each > >>>major project, and each repository is organized in the typical > >>>Subversion fashion... for example, the Asterisk repository is organized > >>>as follows: > >>> > >>>http://svn.digium.com/svn/asterisk/trunk (was CVS HEAD) > >>>http://svn.digium.com/svn/asterisk/branches/1.2 (was CVS v1-2) > >>>http://svn.digium.com/svn/asterisk/tags/1.2.0 (was CVS v1-2-0) > >>> > >>>Other branches and tags are named similarly. Builds of Asterisk made > >>>from the new repositories will report a 'show version' tag made of the > >>>SVN branch name and the repository revision number that was checked out > >>>(unlike the CVS 'show version' tags which incorporated the date/time of > >>>checkout). > >>> > >>>The 'asterisk-cvs' mailing list has been renamed to 'svn-commits' and > >>>will continue to receive commit messages for the all the major projects > >>>on our SVN server (existing subscriptions are still in effect). In > >>>addition, there are new project specific commit mailing lists as well: > >>> > >>> asterisk-commits > >>> asterisk-addons-commits > >>> zaptel-commits > >>> libpri-commits > >>> libiax2-commits > >>> > >>>All of these lists are available on lists.digium.com. Additionally, the > >>>commit messages will contain 'X-SVN-Author' and 'X-SVN-Branch' mail > >>>headers to allow you to sort/filter the commit messages in any way you > >>>wish. > >>> > >>>One of the major benefits of this transition is that we will be opening > >>>up 'developer branches' for Asterisk Development Team members to be able > >>>to work on projects and make them available for public review, testing > >>>and participation; look for another announcement later this week when > >>>that process is ready. > >>> > >>>For the near future, we will continue to provide access to source code > >>>via CVS using the same servers/paths that you have previously been > >>>using; once every day, the relevant Subversion branches will be copied > >>>over into CVS and brought up to date. We expect to keep updating CVS > >>>HEAD this way for three to six months; the other branches will be > >>>maintained for six to nine months. However the CVS repositories will be > >>>updated in a single commit each day and will not contain any detailed > >>>revision history for the changes that are made. We encourage all users > >>>to transition to using Subversion for tracking development as soon as > >>>possible. > >>> > >>>(Special thanks to chipig, sussman, darix, jerenkrantz, eh, mbk and the > >>>others on #svn-dev who helped solve some sticky issues on Saturday > >>>evening of Thanksgiving weekend ) > >>> > >>>___ > >>>--Bandwidth and Colocation provided by Easynews.com -- > >>> > >>>Asterisk-Announce mailing list > >>>To UNSUBSCRIBE or update options visit: > >>> http://lists.digium.com/mailman/listinfo/asterisk-announce > >>> > >>> > >>>-- > >>>Diego Aguirre > >>>Infodag - Informática > >>>FWD#: 459696 > >>>Niko
[AsteriskBrasil] [Fwd: [Asterisk-Announce] Asterisk project converts to Subversion version control system]
On Thursday 01 December 2005 12:29, Josué Conti wrote: > Diego, pelo CVS não se baixa mais nada do *? Tipo como fica agora, por > exemplo? Oi, Josué... veja: > > > For the near future, we will continue to provide access to source code > > > via CVS using the same servers/paths that you have previously been > > > using; once every day, the relevant Subversion branches will be copied > > > over into CVS and brought up to date. We expect to keep updating CVS > > > HEAD this way for three to six months; the other branches will be > > > maintained for six to nine months. However the CVS repositories will be > > > updated in a single commit each day and will not contain any detailed > > > revision history for the changes that are made. "A médio prazo nós continuaremos dando acesso ao código fonte através de CVS, bastando pra isso usar os servidores e caminhos que já eram usados até então; diariamente, os branches relevantes do Subversion serão copiados para dentro do repostiório CVS e atualizados. Esperamos manter atualizado o CVS HEAD dessa forma por 3 meses, ou até 6; os outros branches serão mantidos por 6 meses, podendo chegar a 9. Entretanto, os repositórios CVS serão atualiados de uma vez só, com um único commit por dia, e não conterão informações detalhadas sobre o versionamento dos arquivos" -- Caio Begotti (caio1982) http://caio.ueberalles.net
[AsteriskBrasil] [Fwd: [Asterisk-Announce] Asterisk project converts to Subversion version control system]
Josué, O subversion é bem parecido com o CVS... # svn checkout http://svn.digium.com/svn/asterisk/trunk asterisk # svn checkout http://svn.digium.com/svn/zaptel/trunk zaptel # svn checkout http://svn.digium.com/svn/libpri/trunk libpri para atualizar, segue o mesmo padrão do CVS... # svn update OBS: é necessário ter o SubVersion instalado. não sei quanto as outras distros, mas o Slackware 10.2 já vem com o subversion... Sds, Diego Aguirre Infodag - Informática FWD#: 459696 Nikotel#: 99 21 8138-2710 EnumLookup#: +55 21 8138-2710 DUNDi-br#: 21 8138-2710 Josué Conti escreveu: > Diego, pelo CVS não se baixa mais nada do *? Tipo como fica agora, por > exemplo? > > Abraço > > Josué > > 2005/12/1, Geraldo Fco. do Espírito Santo Jr. : > >>alguem tem a receita de bola para usar o SVN para atualizar o *. >> >>[ ]s >> >>Geraldo >> >>2005/11/30, Diego Aguirre : >> >>>Pessoal, >>> >>>O repositório CVS do asterisk já era, agora é SubVersion... >>> >>> Mensagem Original >>>Assunto: [Asterisk-Announce] Asterisk project converts to Subversion >>>version control system >>>Data: Mon, 28 Nov 2005 13:01:34 -0600 >>>De: Asterisk Development Team >>>Para: asterisk-announce em arizona.digium.com >>> >>>The Asterisk development team is pleased to announce that we have >>>migrated our project repositories and development processes over to the >>>Subversion version control system! >>> >>>Effective immediately, the primary source code distribution point for >>>Asterisk, Zaptel and other related projects (other than release tarballs >>>of course) will be http://svn.digium.com. >>> >>>The actual SVN repositories are available at http://svn.digium.com/svn, >>>and there is a ViewCVS web viewer available at >>>http://svn.digium.com/view. There is a separate repository for each >>>major project, and each repository is organized in the typical >>>Subversion fashion... for example, the Asterisk repository is organized >>>as follows: >>> >>>http://svn.digium.com/svn/asterisk/trunk (was CVS HEAD) >>>http://svn.digium.com/svn/asterisk/branches/1.2 (was CVS v1-2) >>>http://svn.digium.com/svn/asterisk/tags/1.2.0 (was CVS v1-2-0) >>> >>>Other branches and tags are named similarly. Builds of Asterisk made >>>from the new repositories will report a 'show version' tag made of the >>>SVN branch name and the repository revision number that was checked out >>>(unlike the CVS 'show version' tags which incorporated the date/time of >>>checkout). >>> >>>The 'asterisk-cvs' mailing list has been renamed to 'svn-commits' and >>>will continue to receive commit messages for the all the major projects >>>on our SVN server (existing subscriptions are still in effect). In >>>addition, there are new project specific commit mailing lists as well: >>> >>> asterisk-commits >>> asterisk-addons-commits >>> zaptel-commits >>> libpri-commits >>> libiax2-commits >>> >>>All of these lists are available on lists.digium.com. Additionally, the >>>commit messages will contain 'X-SVN-Author' and 'X-SVN-Branch' mail >>>headers to allow you to sort/filter the commit messages in any way you wish. >>> >>>One of the major benefits of this transition is that we will be opening >>>up 'developer branches' for Asterisk Development Team members to be able >>>to work on projects and make them available for public review, testing >>>and participation; look for another announcement later this week when >>>that process is ready. >>> >>>For the near future, we will continue to provide access to source code >>>via CVS using the same servers/paths that you have previously been >>>using; once every day, the relevant Subversion branches will be copied >>>over into CVS and brought up to date. We expect to keep updating CVS >>>HEAD this way for three to six months; the other branches will be >>>maintained for six to nine months. However the CVS repositories will be >>>updated in a single commit each day and will not contain any detailed >>>revision history for the changes that are made. We encourage all users >>>to transition to using Subversion for tracking development as soon as >>>possible. >>> >>>(Special thanks to chipig, sussman, darix, jerenkrantz, eh, mbk and the >>>others on #svn-dev who helped solve some sticky issues on Saturday >>>evening of Thanksgiving weekend ) >>> >>>___ >>>--Bandwidth and Colocation provided by Easynews.com -- >>> >>>Asterisk-Announce mailing list >>>To UNSUBSCRIBE or update options visit: >>> http://lists.digium.com/mailman/listinfo/asterisk-announce >>> >>> >>>-- >>>Diego Aguirre >>>Infodag - Informática >>>FWD#: 459696 >>>Nikotel#: 99 21 8138-2710 >>>EnumLookup#: +55 21 8138-2710 >>>DUNDi-br#: 21 8138-2710 >>> >>> >>> >>> >>> >>>___ >>>Yahoo! doce lar. Faça do Yahoo! sua homepage. >>>http://br.yahoo.com/homepageset.html >>> >>>___ >>>LIsta de discussões AsteriskBrasil.org >>>AsteriskBras
[AsteriskBrasil] [Fwd: [Asterisk-Announce] Asterisk project converts to Subversion version control system]
Dah uma olhada em: http://www.asterisk.org/download []'s On Thursday 01 December 2005 12:29, Josué Conti wrote: > Diego, pelo CVS não se baixa mais nada do *? Tipo como fica agora, por > exemplo? > > Abraço > > Josué > > 2005/12/1, Geraldo Fco. do Espírito Santo Jr. : > > alguem tem a receita de bola para usar o SVN para atualizar o *. > > > > [ ]s > > > > Geraldo > > > > 2005/11/30, Diego Aguirre : > > > Pessoal, > > > > > > O repositório CVS do asterisk já era, agora é SubVersion...
[AsteriskBrasil] [Fwd: [Asterisk-Announce] Asterisk project converts to Subversion version control system]
Diego, pelo CVS não se baixa mais nada do *? Tipo como fica agora, por exemplo? Abraço Josué 2005/12/1, Geraldo Fco. do Espírito Santo Jr. : > alguem tem a receita de bola para usar o SVN para atualizar o *. > > [ ]s > > Geraldo > > 2005/11/30, Diego Aguirre : > > Pessoal, > > > > O repositório CVS do asterisk já era, agora é SubVersion... > > > > Mensagem Original > > Assunto: [Asterisk-Announce] Asterisk project converts to Subversion > > version control system > > Data: Mon, 28 Nov 2005 13:01:34 -0600 > > De: Asterisk Development Team > > Para: asterisk-announce em arizona.digium.com > > > > The Asterisk development team is pleased to announce that we have > > migrated our project repositories and development processes over to the > > Subversion version control system! > > > > Effective immediately, the primary source code distribution point for > > Asterisk, Zaptel and other related projects (other than release tarballs > > of course) will be http://svn.digium.com. > > > > The actual SVN repositories are available at http://svn.digium.com/svn, > > and there is a ViewCVS web viewer available at > > http://svn.digium.com/view. There is a separate repository for each > > major project, and each repository is organized in the typical > > Subversion fashion... for example, the Asterisk repository is organized > > as follows: > > > > http://svn.digium.com/svn/asterisk/trunk (was CVS HEAD) > > http://svn.digium.com/svn/asterisk/branches/1.2 (was CVS v1-2) > > http://svn.digium.com/svn/asterisk/tags/1.2.0 (was CVS v1-2-0) > > > > Other branches and tags are named similarly. Builds of Asterisk made > > from the new repositories will report a 'show version' tag made of the > > SVN branch name and the repository revision number that was checked out > > (unlike the CVS 'show version' tags which incorporated the date/time of > > checkout). > > > > The 'asterisk-cvs' mailing list has been renamed to 'svn-commits' and > > will continue to receive commit messages for the all the major projects > > on our SVN server (existing subscriptions are still in effect). In > > addition, there are new project specific commit mailing lists as well: > > > > asterisk-commits > > asterisk-addons-commits > > zaptel-commits > > libpri-commits > > libiax2-commits > > > > All of these lists are available on lists.digium.com. Additionally, the > > commit messages will contain 'X-SVN-Author' and 'X-SVN-Branch' mail > > headers to allow you to sort/filter the commit messages in any way you wish. > > > > One of the major benefits of this transition is that we will be opening > > up 'developer branches' for Asterisk Development Team members to be able > > to work on projects and make them available for public review, testing > > and participation; look for another announcement later this week when > > that process is ready. > > > > For the near future, we will continue to provide access to source code > > via CVS using the same servers/paths that you have previously been > > using; once every day, the relevant Subversion branches will be copied > > over into CVS and brought up to date. We expect to keep updating CVS > > HEAD this way for three to six months; the other branches will be > > maintained for six to nine months. However the CVS repositories will be > > updated in a single commit each day and will not contain any detailed > > revision history for the changes that are made. We encourage all users > > to transition to using Subversion for tracking development as soon as > > possible. > > > > (Special thanks to chipig, sussman, darix, jerenkrantz, eh, mbk and the > > others on #svn-dev who helped solve some sticky issues on Saturday > > evening of Thanksgiving weekend ) > > > > ___ > > --Bandwidth and Colocation provided by Easynews.com -- > > > > Asterisk-Announce mailing list > > To UNSUBSCRIBE or update options visit: > > http://lists.digium.com/mailman/listinfo/asterisk-announce > > > > > > -- > > Diego Aguirre > > Infodag - Informática > > FWD#: 459696 > > Nikotel#: 99 21 8138-2710 > > EnumLookup#: +55 21 8138-2710 > > DUNDi-br#: 21 8138-2710 > > > > > > > > > > > > ___ > > Yahoo! doce lar. Faça do Yahoo! sua homepage. > > http://br.yahoo.com/homepageset.html > > > > ___ > > LIsta de discussões AsteriskBrasil.org > > AsteriskBrasil em listas.asteriskbrasil.org > > http://listas.asteriskbrasil.org/mailman/listinfo/asteriskbrasil > > > > ___ > > Acesse o wiki AsteriskBrasil.org: > > http://www.asteriskbrasil.org > > > ___ > LIsta de discussões AsteriskBrasil.org > AsteriskBrasil em listas.asteriskbrasil.org > http://listas.asteriskbrasil.org/mailman/listinfo/asteriskbrasil > > ___ > Acesse o wiki AsteriskBrasil.org: > http://www.
[AsteriskBrasil] [Fwd: [Asterisk-Announce] Asterisk project converts to Subversion version control system]
alguem tem a receita de bola para usar o SVN para atualizar o *. [ ]s Geraldo 2005/11/30, Diego Aguirre : > Pessoal, > > O repositório CVS do asterisk já era, agora é SubVersion... > > Mensagem Original > Assunto: [Asterisk-Announce] Asterisk project converts to Subversion > version control system > Data: Mon, 28 Nov 2005 13:01:34 -0600 > De: Asterisk Development Team > Para: asterisk-announce em arizona.digium.com > > The Asterisk development team is pleased to announce that we have > migrated our project repositories and development processes over to the > Subversion version control system! > > Effective immediately, the primary source code distribution point for > Asterisk, Zaptel and other related projects (other than release tarballs > of course) will be http://svn.digium.com. > > The actual SVN repositories are available at http://svn.digium.com/svn, > and there is a ViewCVS web viewer available at > http://svn.digium.com/view. There is a separate repository for each > major project, and each repository is organized in the typical > Subversion fashion... for example, the Asterisk repository is organized > as follows: > > http://svn.digium.com/svn/asterisk/trunk (was CVS HEAD) > http://svn.digium.com/svn/asterisk/branches/1.2 (was CVS v1-2) > http://svn.digium.com/svn/asterisk/tags/1.2.0 (was CVS v1-2-0) > > Other branches and tags are named similarly. Builds of Asterisk made > from the new repositories will report a 'show version' tag made of the > SVN branch name and the repository revision number that was checked out > (unlike the CVS 'show version' tags which incorporated the date/time of > checkout). > > The 'asterisk-cvs' mailing list has been renamed to 'svn-commits' and > will continue to receive commit messages for the all the major projects > on our SVN server (existing subscriptions are still in effect). In > addition, there are new project specific commit mailing lists as well: > > asterisk-commits > asterisk-addons-commits > zaptel-commits > libpri-commits > libiax2-commits > > All of these lists are available on lists.digium.com. Additionally, the > commit messages will contain 'X-SVN-Author' and 'X-SVN-Branch' mail > headers to allow you to sort/filter the commit messages in any way you wish. > > One of the major benefits of this transition is that we will be opening > up 'developer branches' for Asterisk Development Team members to be able > to work on projects and make them available for public review, testing > and participation; look for another announcement later this week when > that process is ready. > > For the near future, we will continue to provide access to source code > via CVS using the same servers/paths that you have previously been > using; once every day, the relevant Subversion branches will be copied > over into CVS and brought up to date. We expect to keep updating CVS > HEAD this way for three to six months; the other branches will be > maintained for six to nine months. However the CVS repositories will be > updated in a single commit each day and will not contain any detailed > revision history for the changes that are made. We encourage all users > to transition to using Subversion for tracking development as soon as > possible. > > (Special thanks to chipig, sussman, darix, jerenkrantz, eh, mbk and the > others on #svn-dev who helped solve some sticky issues on Saturday > evening of Thanksgiving weekend ) > > ___ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Announce mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-announce > > > -- > Diego Aguirre > Infodag - Informática > FWD#: 459696 > Nikotel#: 99 21 8138-2710 > EnumLookup#: +55 21 8138-2710 > DUNDi-br#: 21 8138-2710 > > > > > > ___ > Yahoo! doce lar. Faça do Yahoo! sua homepage. > http://br.yahoo.com/homepageset.html > > ___ > LIsta de discussões AsteriskBrasil.org > AsteriskBrasil em listas.asteriskbrasil.org > http://listas.asteriskbrasil.org/mailman/listinfo/asteriskbrasil > > ___ > Acesse o wiki AsteriskBrasil.org: > http://www.asteriskbrasil.org >
[AsteriskBrasil] [Fwd: [Asterisk-Announce] Asterisk project converts to Subversion version control system]
Pessoal, O repositório CVS do asterisk já era, agora é SubVersion... Mensagem Original Assunto: [Asterisk-Announce] Asterisk project converts to Subversion version control system Data: Mon, 28 Nov 2005 13:01:34 -0600 De: Asterisk Development Team Para: asterisk-announce em arizona.digium.com The Asterisk development team is pleased to announce that we have migrated our project repositories and development processes over to the Subversion version control system! Effective immediately, the primary source code distribution point for Asterisk, Zaptel and other related projects (other than release tarballs of course) will be http://svn.digium.com. The actual SVN repositories are available at http://svn.digium.com/svn, and there is a ViewCVS web viewer available at http://svn.digium.com/view. There is a separate repository for each major project, and each repository is organized in the typical Subversion fashion... for example, the Asterisk repository is organized as follows: http://svn.digium.com/svn/asterisk/trunk (was CVS HEAD) http://svn.digium.com/svn/asterisk/branches/1.2 (was CVS v1-2) http://svn.digium.com/svn/asterisk/tags/1.2.0 (was CVS v1-2-0) Other branches and tags are named similarly. Builds of Asterisk made from the new repositories will report a 'show version' tag made of the SVN branch name and the repository revision number that was checked out (unlike the CVS 'show version' tags which incorporated the date/time of checkout). The 'asterisk-cvs' mailing list has been renamed to 'svn-commits' and will continue to receive commit messages for the all the major projects on our SVN server (existing subscriptions are still in effect). In addition, there are new project specific commit mailing lists as well: asterisk-commits asterisk-addons-commits zaptel-commits libpri-commits libiax2-commits All of these lists are available on lists.digium.com. Additionally, the commit messages will contain 'X-SVN-Author' and 'X-SVN-Branch' mail headers to allow you to sort/filter the commit messages in any way you wish. One of the major benefits of this transition is that we will be opening up 'developer branches' for Asterisk Development Team members to be able to work on projects and make them available for public review, testing and participation; look for another announcement later this week when that process is ready. For the near future, we will continue to provide access to source code via CVS using the same servers/paths that you have previously been using; once every day, the relevant Subversion branches will be copied over into CVS and brought up to date. We expect to keep updating CVS HEAD this way for three to six months; the other branches will be maintained for six to nine months. However the CVS repositories will be updated in a single commit each day and will not contain any detailed revision history for the changes that are made. We encourage all users to transition to using Subversion for tracking development as soon as possible. (Special thanks to chipig, sussman, darix, jerenkrantz, eh, mbk and the others on #svn-dev who helped solve some sticky issues on Saturday evening of Thanksgiving weekend ) ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Announce mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-announce -- Diego Aguirre Infodag - Informática FWD#: 459696 Nikotel#: 99 21 8138-2710 EnumLookup#: +55 21 8138-2710 DUNDi-br#: 21 8138-2710 ___ Yahoo! doce lar. Faça do Yahoo! sua homepage. http://br.yahoo.com/homepageset.html
