For the past two days I’ve been struggling with my screen resolution of 800×600.
I tried to download a driver for the ATI RAGE XL rev 27.
lspci showed me the following:
02:01.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
I tried to find a driver for it, but couldn’t find.
I guess, there’s no support for it anymore, though I’m not sure.
.svn ???
Let’s see wat this has to do with the subversion repository. . .
.svn is quite like an administrative area, something like the metadata . . .
This will not be listed normally with the files in the repository.Subversion depends on it to manage the working copy.
If we accidentally remove the .svn subdirectory, the easiest way to fix the problem is to remove the entire containing directory (a normal system deletion, not svn delete), then run “svn update” from a parent directory. The Subversion client
will download the directory you’ve deleted, with a new .svn area as well.
“.svn” lets us to manage our working copy even when our repo is in some other network and the working copy is in our local machine, while we are out of network.
we can use the commands “svn status”, “svn diff”, and “svn revert” without any network access.
Since I’m not a stranger to the Subversion, the first chapter of the book was pretty easy for me to catch up.
Since some of my friends were strangers to the Subversion, we had a short Knowledge Transfer (KT) in which I gave them an introduction to the Subversion.
A few points about it. . .
Earlier the lock – modify – unlock concept was used, which eventually had some drawbacks. The main reason being that, the file gets LOCKED by the user preventing the other user from editing the same file simultaneously. The other users had to wait for the first user to commit his/her work even though there is no need practically.
The subversion uses the COPY – MODIFY – MERGE concept, which needs some manual effort to prevent the conflicts.
Subversion uses the Berkeley DB and the FSFS database for the repository.
Let me tel u the basic commands covered in it too 🙂
1. svnadmin create /var/svn/repos
( svnadmin is the function in subversion to perform the admin related works such as creating a repository. Here a new repository is created in the name “repos” )
2. svn add test.c
( svn add is a funcion to add a new file into the subversion repository. Here a new c code is added into the reposiory. NOTE : this command must be run from inside the working copy )
3. svn co file:///var/svn/repos testrepo
( svn co is a function to checkout the latest revision from the subversion repostiory. Here the files are checkedout to a new directory named “testrepo”. NOTE: this command must be run from inside the working copy )
NOTE: a metafile .svn is created automatically when we checkout a repository.
4. svn update
( svn update is a function to update our current working copy comparing it to the subversion repository NOTE : this command must be run from inside the working copy)
I have just installed the Debian Lenny in my office desktop.
Configured the iitk debian mirror to manage the packages.
deb http://mirror.cse.iitk.ac.in/debian lenny main contrib non-free
Obviously, installed the subversion in my desktop.
Now I just wished to download the source code the subversion.
Checked out the latest source code by,
svn co http://svn.apache.org/repos/asf/subversion/trunk subversion
Awesome !!! the checked out version was 987467
Since I am in the subversion development team, I have to learn the basics of the subversion and have to be very strong in it. Though I’ve used the subversion even before for my DRDO projects, I’m not exposed to the development side of the subversion.
I’m proud to work under a subversion commiter, Mr.Kamesh.
To start with the basics, I’ve downloaded the “Version Control with Subversion 1.6” book.
Just started with it… Soon will be a good developer !!!
Hey all. . . I am now a part of the CollabNet . 🙂
Joined here as a trainee software engineer.
It’s really great to be here, that too with really great people.
known is a drop 