Life at Cisco

Partial import from SVN to GIT with history and multiple branches

GIT comes with some nice built in functionality for importing into GIT from SVN, but when you break outside the expected, things get a little weird, a little fast.

I have been doing some migrations of some of a code base from SVN to GIT, but in keeping with the GIT best practices, each artifact gets its own repo, unlike SVN, where everything typically lives in one monolithic hierarchy.

This does not work out of the box, using the basic options. You will want to follow the bit about creating a users.txt file, and the parts for converting tags and branches to GIT branches, however for the clone itself, I found this to work better for me:

git svn clone https://your-svn-server/path/to/repo/ -T path/to/sub-tree/that/is/being/imported –authors-file=users.txt –no-metadata

Hope that helps someone, and maybe even me when I need to do it again and cannot remember how…

How to tell everyone what an idiot you are

Hit reply-to-all on an email that you have not read.

This email went out to (what I now know is) a large email alias about a migration of information. Apparently there are many people on the alias who do not know what to do about this information or why they are getting the email. So they replied. To everyone. So far over 100 have replied. To all.

And the kicker is, the email clearly says that this migration will happen automatically, and you probably do not need to do anything. If you do need to do anything, an email will be sent to you with details and instructions on exactly what to do.

At this point, the number of people replying to all, pleading with others to stop replying to all is running neck and neck with the number of people replying to all to say that they don’t know why they got this email. if you don’t get the irony, please stop reading my blog – you won’t understand most of what I have to say.

I think that the best reply to all was a random recipe…

I love screen real estate

It is all about real estate… Another hundred bucks would go a long way toward increasing productivity. I would trade that for the CD-RW drive!

Seriously, 1024×768 is just not enough screen – you only get a dozen lines of code with the IDE around it. 1280×1024 is just enough to start with, but 1400×1050 or 1600×1200 is the sweet spot. I guess I am too much of a code junkie, but the extra lines of code go that extra mile towards making code crafting that much easier.

On the plus side, I should be able to land a good monitor – the one that is on my desk now is good except for the severe wobble on the top half (yes, only the top half) of the screen 😉

Day three

Well the laptop is here – oh wait, no, the port replicator, extra power cord, and lock are here. The laptop is still MIA.

The lunch cafe is very convinient – don’t even need to leave the building, just walk downstairs. Decent prices for what you get too.

Second day on the job

Well more of the sites are available today, and after I put in a trouble ticket, the New Hire Orientation was available. Pretty informative – and I got over 80% on the exit exam :) Also finished the health benefits section – easiest that I have ever done – having it all online is great – no paperwork. Finished all the documentation and filled out my first PTO request – hope they let me go negative…

Still no laptop – that should be here tomorrow…

First day at Cisco

Overall, a pretty good first day, all things considered.

Lots of documentation to read – PRD and specifications. Not all the passwords have propagated yet, so I cannot login to all the sites, but read alot of orientation materials. They do not have a laptop for me yet, so I am using my own for now. That should get here Thursday – but hey, I have a good monitor when the laptop does get here 😉

Went out after lunch with some of the remote people from the group, so I guess it was a good week to join.