Rasmus Lerdorf schrieb:
Lukas Kahwe Smith wrote:
The git and hg integration with svn is also good so any developer who
prefers to have a local repository can very easily use either git or
hg and easily merge into the central svn repository.
However I think we should provide the
On 25.07.2008, at 12:44, Gwynne Raskind wrote:
On Jul 25, 2008, at 6:34 AM, Hannes Magnusson wrote:
At this point it's clear that moving from CVS to SVN for PHP has
become a
more or less official project.
Has the phpdoc revision/translation problem been looked into/fixed?
No, not yet,
Hello Travis,
Friday, July 25, 2008, 9:27:02 PM, you wrote:
Hello Marcus;
Marcus Boerger wrote:
A cvs read-only mirror would be nice to allow the old way of checking out
stuff. But there I fail to see the reason to limit our selves to one
additional other tool, nor do I see a reason to
On Fri, Jul 25, 2008 at 5:06 AM, Gwynne Raskind
[EMAIL PROTECTED] wrote:
At this point it's clear that moving from CVS to SVN for PHP has become a
more or less official project. As such, there is a new mailing list
isn't better to migrate to git or mercurial ?
marius popa wrote:
On Fri, Jul 25, 2008 at 5:06 AM, Gwynne Raskind
[EMAIL PROTECTED] wrote:
At this point it's clear that moving from CVS to SVN for PHP has become a
more or less official project. As such, there is a new mailing list
isn't better to migrate to git or mercurial ?
On 25.07.2008, at 09:48, Rasmus Lerdorf wrote:
marius popa wrote:
On Fri, Jul 25, 2008 at 5:06 AM, Gwynne Raskind
[EMAIL PROTECTED] wrote:
At this point it's clear that moving from CVS to SVN for PHP has
become a
more or less official project. As such, there is a new mailing list
isn't
Lukas Kahwe Smith wrote:
The git and hg integration with svn is also good so any developer who
prefers to have a local repository can very easily use either git or
hg and easily merge into the central svn repository.
However I think we should provide the infrastructure for developers to
setup
On 25.07.2008, at 10:11, Rasmus Lerdorf wrote:
Lukas Kahwe Smith wrote:
The git and hg integration with svn is also good so any developer
who
prefers to have a local repository can very easily use either git or
hg and easily merge into the central svn repository.
However I think we
However I think we should provide the infrastructure for developers to
setup a dvcs. I dont know if we want to standardize on a specific one.
But collaboration on exterimental stuff that requires a dvcs should be
possible on php.net servers.
Maybe it's just about having the possibilities for
On 25.07.2008, at 10:25, Lars Strojny wrote:
Hi Rasmus,
Am Freitag, den 25.07.2008, 01:11 -0700 schrieb Rasmus Lerdorf:
[...]
What do you mean by that? hgsvn and git-svn don't need any server-
side
support to enable you to work locally and do local git or hg checkins
and then sync to the
Hi,
David Soria Parra wrote:
However I think we should provide the infrastructure for developers to
setup a dvcs. I dont know if we want to standardize on a specific one.
But collaboration on exterimental stuff that requires a dvcs should be
possible on php.net servers.
Maybe it's just
Hello Lukas,
Friday, July 25, 2008, 10:26:59 AM, you wrote:
On 25.07.2008, at 10:25, Lars Strojny wrote:
Hi Rasmus,
Am Freitag, den 25.07.2008, 01:11 -0700 schrieb Rasmus Lerdorf:
[...]
What do you mean by that? hgsvn and git-svn don't need any server-
side
support to enable you to
On 25.07.2008, at 11:46, Marcus Boerger wrote:
I mean that if several people work on a changeset, that they still
might want to have a join central repo. Of course dvcs allows direct
exchange of patches as well, but it might still be a good idea to
have
this central dvcs repo for historical
On Fri, 2008-07-25 at 10:26 +0200, David Soria Parra wrote:
However I think we should provide the infrastructure for developers to
setup a dvcs. I dont know if we want to standardize on a specific one.
But collaboration on exterimental stuff that requires a dvcs should be
possible on
On Fri, Jul 25, 2008 at 04:06, Gwynne Raskind
[EMAIL PROTECTED] wrote:
At this point it's clear that moving from CVS to SVN for PHP has become a
more or less official project.
Has the phpdoc revision/translation problem been looked into/fixed?
-Hannes
--
PHP Internals - PHP Runtime
On 25 Jul 2008, at 10:58, Lukas Kahwe Smith wrote:
On 25.07.2008, at 11:46, Marcus Boerger wrote:
I mean that if several people work on a changeset, that they still
might want to have a join central repo. Of course dvcs allows direct
exchange of patches as well, but it might still be a good
On Jul 25, 2008, at 6:34 AM, Hannes Magnusson wrote:
At this point it's clear that moving from CVS to SVN for PHP has
become a
more or less official project.
Has the phpdoc revision/translation problem been looked into/fixed?
No, not yet, but it will have to be. I intend for discussion on
On 25.07.2008, at 12:41, Scott MacVicar wrote:
On 25 Jul 2008, at 10:58, Lukas Kahwe Smith wrote:
On 25.07.2008, at 11:46, Marcus Boerger wrote:
I mean that if several people work on a changeset, that they still
might want to have a join central repo. Of course dvcs allows
direct
Hi Lukas,
We have already had several cases in the past where developers have
collaborated on a CVS branch. The main reason why this hasn't been
common practice is because CVS branching sucks and because some
developers didn't feel comfortable with using branches regardless of the
tool.
I think
Hello Lukas,
Friday, July 25, 2008, 11:58:42 AM, you wrote:
On 25.07.2008, at 11:46, Marcus Boerger wrote:
I mean that if several people work on a changeset, that they still
might want to have a join central repo. Of course dvcs allows direct
exchange of patches as well, but it might still
On Fri, Jul 25, 2008 at 5:15 AM, Richard Quadling
[EMAIL PROTECTED] wrote:
As a windows user my observations/opinions are ...
taken with a grain of salt. ;-P
Isn't discussion about how to add on to SVN and which tools will
be better-suited for development a decade from now
Hello Marcus;
Marcus Boerger wrote:
A cvs read-only mirror would be nice to allow the old way of checking out
stuff. But there I fail to see the reason to limit our selves to one
additional other tool, nor do I see a reason to complicate matters even
more by giving people other repositories
At this point it's clear that moving from CVS to SVN for PHP has
become a more or less official project. As such, there is a new
mailing list [EMAIL PROTECTED] for anyone who wants to
help with the move. If you're familiar with what I've already done so
far
23 matches
Mail list logo
