Hi all- This weekend we will be migrating our source repository from using CVS to Subversion. This migration will take place starting Friday evening at 5PM and continue through Saturday. More details will follow. After the migration is complete, in order to check out the WebKit sources you will be required to have a Subversion client on your machine. Since we know you'll all be anxious to checkout the sources once complete, this is an early reminder to start downloading your subversion client. :) Subversion Manual: http://svnbook.red-bean.com/ Mac OS X Subversion Client Packages: http://www.codingmonkeys.de/mbo/ http://subversion.tigris.org/project_packages.html -eric
1. Apple won't be providing their own build of a Subversion client for Tiger, not even to developers? 2. Are there any best practices, lessons learned or perhaps a white paper that you can share about the CVS to Subversion conversion process? Dave On Mon, Dec 05, 2005 at 01:08:15PM -0800, Eric Seidel wrote:
Hi all-
This weekend we will be migrating our source repository from using CVS to Subversion. This migration will take place starting Friday evening at 5PM and continue through Saturday. More details will follow.
After the migration is complete, in order to check out the WebKit sources you will be required to have a Subversion client on your machine. Since we know you'll all be anxious to checkout the sources once complete, this is an early reminder to start downloading your subversion client. :)
Subversion Manual: http://svnbook.red-bean.com/
Mac OS X Subversion Client Packages: http://www.codingmonkeys.de/mbo/ http://subversion.tigris.org/project_packages.html
-eric
Can't answer 1 for you, 2 though: my experience is that switching from CVS to SVN is actually very easy. The branching stuff is different, but you probably won't use that, in general it's just replacing "cvs" by "svn" in your favourite command and it works :). Kind regards, Joost -- Joost de Valk #: AlthA on #webkit @ irc.freenode.net @: webkit@joostdevalk.nl W: http://www.joostdevalk.nl "The only people who find what they are looking for in life are the fault finders." - Foster's Law On Dec 5, 2005, at 11:56 PM, David D. Kilzer wrote:
1. Apple won't be providing their own build of a Subversion client for Tiger, not even to developers?
2. Are there any best practices, lessons learned or perhaps a white paper that you can share about the CVS to Subversion conversion process?
Dave
On Mon, Dec 05, 2005 at 01:08:15PM -0800, Eric Seidel wrote:
Hi all-
This weekend we will be migrating our source repository from using CVS to Subversion. This migration will take place starting Friday evening at 5PM and continue through Saturday. More details will follow.
After the migration is complete, in order to check out the WebKit sources you will be required to have a Subversion client on your machine. Since we know you'll all be anxious to checkout the sources once complete, this is an early reminder to start downloading your subversion client. :)
Subversion Manual: http://svnbook.red-bean.com/
Mac OS X Subversion Client Packages: http://www.codingmonkeys.de/mbo/ http://subversion.tigris.org/project_packages.html
-eric
_______________________________________________ webkit-dev mailing list webkit-dev@opendarwin.org http://www.opendarwin.org/mailman/listinfo/webkit-dev
Actually, I was looking for best practices and lessons learned for converting a CVS repository to a Subversion repository if there was an information that could be shared. Stuff like: 1. Reconnecting history of files that were deleted and added in the "same" commit. 2. Handling *.,v files that have been copied from the server side (instead of deleting and adding them as in #1). I've used Subversion at work recently. It does take some getting used to (some concepts like branching are implemented much differently and yet much more simply), but overall I like it a lot better than CVS. It really does fix a lot of the warts that CVS has. Dave On Tue, Dec 06, 2005 at 07:47:42AM +0100, Joost de Valk wrote:
Can't answer 1 for you, 2 though: my experience is that switching from CVS to SVN is actually very easy. The branching stuff is different, but you probably won't use that, in general it's just replacing "cvs" by "svn" in your favourite command and it works :).
Kind regards, Joost
-- Joost de Valk
#: AlthA on #webkit @ irc.freenode.net @: webkit@joostdevalk.nl W: http://www.joostdevalk.nl
"The only people who find what they are looking for in life are the fault finders." - Foster's Law
On Dec 5, 2005, at 11:56 PM, David D. Kilzer wrote:
1. Apple won't be providing their own build of a Subversion client for Tiger, not even to developers?
2. Are there any best practices, lessons learned or perhaps a white paper that you can share about the CVS to Subversion conversion process?
Dave
On Mon, Dec 05, 2005 at 01:08:15PM -0800, Eric Seidel wrote:
Hi all-
This weekend we will be migrating our source repository from using CVS to Subversion. This migration will take place starting Friday evening at 5PM and continue through Saturday. More details will follow.
After the migration is complete, in order to check out the WebKit sources you will be required to have a Subversion client on your machine. Since we know you'll all be anxious to checkout the sources once complete, this is an early reminder to start downloading your subversion client. :)
Subversion Manual: http://svnbook.red-bean.com/
Mac OS X Subversion Client Packages: http://www.codingmonkeys.de/mbo/ http://subversion.tigris.org/project_packages.html
-eric
The cvs2svn script (http://cvs2svn.tigris.org/) iterates through all the commits and makes change sets from commits in the same time frame that also have the same commit message. There are a few other migration scripts floating around that do the same thing. The migration scripts don't take server side moves into account, they will show up as 2 files with disconnected history. — Timothy Hatcher On Dec 6, 2005, at 10:36 AM, David D. Kilzer wrote:
Actually, I was looking for best practices and lessons learned for converting a CVS repository to a Subversion repository if there was an information that could be shared. Stuff like:
1. Reconnecting history of files that were deleted and added in the "same" commit.
2. Handling *.,v files that have been copied from the server side (instead of deleting and adding them as in #1).
I've used Subversion at work recently. It does take some getting used to (some concepts like branching are implemented much differently and yet much more simply), but overall I like it a lot better than CVS. It really does fix a lot of the warts that CVS has.
Dave
On Tue, Dec 06, 2005 at 07:47:42AM +0100, Joost de Valk wrote:
Can't answer 1 for you, 2 though: my experience is that switching from CVS to SVN is actually very easy. The branching stuff is different, but you probably won't use that, in general it's just replacing "cvs" by "svn" in your favourite command and it works :).
Kind regards, Joost
-- Joost de Valk
#: AlthA on #webkit @ irc.freenode.net @: webkit@joostdevalk.nl W: http://www.joostdevalk.nl
"The only people who find what they are looking for in life are the fault finders." - Foster's Law
On Dec 5, 2005, at 11:56 PM, David D. Kilzer wrote:
1. Apple won't be providing their own build of a Subversion client for Tiger, not even to developers?
2. Are there any best practices, lessons learned or perhaps a white paper that you can share about the CVS to Subversion conversion process?
Dave
On Mon, Dec 05, 2005 at 01:08:15PM -0800, Eric Seidel wrote:
Hi all-
This weekend we will be migrating our source repository from using CVS to Subversion. This migration will take place starting Friday evening at 5PM and continue through Saturday. More details will follow.
After the migration is complete, in order to check out the WebKit sources you will be required to have a Subversion client on your machine. Since we know you'll all be anxious to checkout the sources once complete, this is an early reminder to start downloading your subversion client. :)
Subversion Manual: http://svnbook.red-bean.com/
Mac OS X Subversion Client Packages: http://www.codingmonkeys.de/mbo/ http://subversion.tigris.org/project_packages.html
-eric
_______________________________________________ webkit-dev mailing list webkit-dev@opendarwin.org http://www.opendarwin.org/mailman/listinfo/webkit-dev
Be careful when using cvs2svn. We got burned by it when it inserted a filename containing DEL near the beginning of the repo. The main problem with it is that it doesn't go through svn's regular input checking, it feeds the repo directly. -Colin www.adiumx.com On Dec 6, 2005, at 1:45 PM, Timothy Hatcher wrote:
The cvs2svn script (http://cvs2svn.tigris.org/) iterates through all the commits and makes change sets from commits in the same time frame that also have the same commit message. There are a few other migration scripts floating around that do the same thing. The migration scripts don't take server side moves into account, they will show up as 2 files with disconnected history.
— Timothy Hatcher
On Dec 6, 2005, at 10:36 AM, David D. Kilzer wrote:
Actually, I was looking for best practices and lessons learned for converting a CVS repository to a Subversion repository if there was an information that could be shared. Stuff like:
1. Reconnecting history of files that were deleted and added in the "same" commit.
2. Handling *.,v files that have been copied from the server side (instead of deleting and adding them as in #1).
I've used Subversion at work recently. It does take some getting used to (some concepts like branching are implemented much differently and yet much more simply), but overall I like it a lot better than CVS. It really does fix a lot of the warts that CVS has.
Dave
On Tue, Dec 06, 2005 at 07:47:42AM +0100, Joost de Valk wrote:
Can't answer 1 for you, 2 though: my experience is that switching from CVS to SVN is actually very easy. The branching stuff is different, but you probably won't use that, in general it's just replacing "cvs" by "svn" in your favourite command and it works :).
Kind regards, Joost
-- Joost de Valk
#: AlthA on #webkit @ irc.freenode.net @: webkit@joostdevalk.nl W: http://www.joostdevalk.nl
"The only people who find what they are looking for in life are the fault finders." - Foster's Law
On Dec 5, 2005, at 11:56 PM, David D. Kilzer wrote:
1. Apple won't be providing their own build of a Subversion client for Tiger, not even to developers?
2. Are there any best practices, lessons learned or perhaps a white paper that you can share about the CVS to Subversion conversion process?
Dave
On Mon, Dec 05, 2005 at 01:08:15PM -0800, Eric Seidel wrote:
Hi all-
This weekend we will be migrating our source repository from using CVS to Subversion. This migration will take place starting Friday evening at 5PM and continue through Saturday. More details will follow.
After the migration is complete, in order to check out the WebKit sources you will be required to have a Subversion client on your machine. Since we know you'll all be anxious to checkout the sources once complete, this is an early reminder to start downloading your subversion client. :)
Subversion Manual: http://svnbook.red-bean.com/
Mac OS X Subversion Client Packages: http://www.codingmonkeys.de/mbo/ http://subversion.tigris.org/project_packages.html
-eric
_______________________________________________ webkit-dev mailing list webkit-dev@opendarwin.org http://www.opendarwin.org/mailman/listinfo/webkit-dev
_______________________________________________ webkit-dev mailing list webkit-dev@opendarwin.org http://www.opendarwin.org/mailman/listinfo/webkit-dev
On Dec 5, 2005, at 5:56 PM, David D. Kilzer wrote:
1. Apple won't be providing their own build of a Subversion client for Tiger, not even to developers?
No clue if Apple will be, but you can download a pre-built SVN binary here: http://metissian.com/projects/macosx/subversion/ -Colin www.adiumx.com
On Dec 5, 2005, at 2:56 PM, David D. Kilzer wrote:
1. Apple won't be providing their own build of a Subversion client for Tiger, not even to developers?
Not to my knowledge. http://www.codingmonkeys.de/mbo/ is the best place I know of to get pre-packaged installs.
2. Are there any best practices, lessons learned or perhaps a white paper that you can share about the CVS to Subversion conversion process?
Tim basically covered it. We just used cvs2svn the python script.
Dave
On Mon, Dec 05, 2005 at 01:08:15PM -0800, Eric Seidel wrote:
Hi all-
This weekend we will be migrating our source repository from using CVS to Subversion. This migration will take place starting Friday evening at 5PM and continue through Saturday. More details will follow.
After the migration is complete, in order to check out the WebKit sources you will be required to have a Subversion client on your machine. Since we know you'll all be anxious to checkout the sources once complete, this is an early reminder to start downloading your subversion client. :)
Subversion Manual: http://svnbook.red-bean.com/
Mac OS X Subversion Client Packages: http://www.codingmonkeys.de/mbo/ http://subversion.tigris.org/project_packages.html
-eric
On Dec 6, 2005, at 5:00 PM, Eric Seidel wrote:
Not to my knowledge. http://www.codingmonkeys.de/mbo/ is the best place I know of to get pre-packaged installs.
The "official" (linked to from the svn website) location is http:// metissian.com/projects/macosx/subversion/ -Colin
participants (5)
-
Colin Barrett
-
ddkilzer＠kilzer.net
-
Eric Seidel
-
Joost de Valk
-
Timothy Hatcher