Renaming H.EXE
Jason Barile, test lead for the new Microsoft Visual Studio Team Foundation source control application (codename, Hatteras) asks a tantalizing little question,
“Anyone have suggestions for a cmd line executable name?”
As Jason points out, h commandname “.. .is the working name for our command line executable, and it's a short version of “Hatteras”. It is unlikely, though not impossible, that we will ship “h“ with Microsoft Team Foundation for the following reasons:
- h is the abbreviated name of a project codename. Microsoft doesn't ship codenames.
- h is the nickname of a highly addictive substance. And whereas Hatteras can be addictive to computer geeks, it's definitely not a drug and it's certainly good for your health.
So, do you want to make your mark? Go for the mainline. Suggest a name. My suggestion is hr.exe because Hatteras is going to be a homerun. Strike that. Human Resources would be all over us for that. ;-)
Comments
- Anonymous
July 12, 2004
How about SoCo.EXE (for SOurce COntrol, not Southern Comfort...) :) - Anonymous
July 12, 2004
sc? - Anonymous
July 12, 2004
The comment has been removed - Anonymous
July 12, 2004
The comment has been removed - Anonymous
July 12, 2004
The comment has been removed - Anonymous
July 12, 2004
That's precisely why I suggested "SCM" for the client-side and "SCMS" for the server-side. (See Jason's blog article...) - Anonymous
July 16, 2004
scc for client? Perhaps that could be confused for a C compiler though. - Anonymous
July 22, 2004
SCC? VSTF is good, too. - Anonymous
July 29, 2005
How about TSSC.
MSESC (MS Enterprise Source Control)... better than MESC which would be too much like H. - Anonymous
April 28, 2006
source control