subversion migration

On Oct 17, 2005 I posted about gcc being converted from cvs to subversion.

http://malayamaarutham.blogspot.com/2005/10/gcc-cvs-svn.html

In that post, I also stated that I should be migrating to subversion. Well, It finally happened after about 6 months :-) I finally created a subversion repository and migrated couple of my previous projects to subversion. Things look very cool so far!

The documentation for svn is available at http://svnbook.red-bean.com/

In particular, I was impressed with http://svnbook.red-bean.com/nightly/en/svn.intro.quickstart.html which gives an headstart for CVS users.

Go subversion go! You rock!

bug reports summary

The reports are organized in reverse chronological order so that the latest stay on the top.

Bugs reported and not yet fixed

• http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404635 reported on Dec 26, 2006.
  
• http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404535 reported on Dec 25, 2006.
  
• http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404450 reported on Dec 24, 2006.
  
• https://savannah.gnu.org/bugs/?18363 reported on Nov 24, 2006.
• http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399903 reported on Nov 22, 2006.
• http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399653 reported on Nov 21, 2006.
  
• http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397078 reported on Nov 04, 2006.
• http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=396802 reported on Nov 02, 2006.
• http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393481 reported on Oct 16, 2006.

Bugs reported and fixed (sorted in the order when they are fixed).

• http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=374023 reported on Jun 16, 2006; fixed by Jan 18, 2007
  
• http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364900 reported on Apr 26, 2006; fixed by Oct 25, 2006
• http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=363642 reported on Apr 20, 2006; fixed by Jun 03, 2006
  
• http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343969 reported on Sep 30, 2005; fixed by Jun 02, 2006
• http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357685 reported on Mar 18, 2006; fixed by Apr 20, 2006

This post is last updated on Jan 18, 2007.

"adsense for search" now included in this blogspot

Of late, I have been posting a lot of stuff on this blog. Now I am at a stage, where, I cannot recall all the articles/issues/musings that have previously been posted. So, I decided to put a google search box in my blog. This search box is a bit different from the default search box provided by blogger.

The default search box that comes with blogger provides two functionalities:

1. Search this blog
2. Search all blogs

But it does not allow me to search the web.

The google search box also provides two functionalities:

1. Search this blog
   
2. Search the whole web
   

As the second option is useful to me, I decided to have google search box in my blog.

Google calls this search box as "adsense for search". Yesterday, I did some css hacking and now my blog is "adsense for search" compliant. The search bar should appear on the right of this blog in the "sidebar".

Any comments regarding this move are most welcome.

On a related note, Sometime ago, I have included "adsense for content" - ie advertisements in this blog. The related post can be found at

http://malayamaarutham.blogspot.com/2005/11/this-blog-is-now-adsense-friendly.html


raju

gmail feature suggestions - 4

Please provide instructions for accessing gmail using kmail as the email client. The relevant instructions can go into http://mail.google.com/support/bin/topic.py?topic=1555

Currently there is only http://mail.google.com/support/bin/answer.py?answer=13287

But this is very unclear. Should one use TLS or SSL when using kmail as their MUA? Also kmail provides 6 different authentication mechanisms such as LOGIN, PLAIN, CRAM-MD5, DIGEST-MD5, NTLM, GSSAPI. It is not clear as to what authentication mechanism one should use with kmail.

raju