On Wed, Aug 27, 2008 at 11:27:04AM -0400, Steven Rostedt wrote:
quoted text
> 
> On Tue, 26 Aug 2008, Perry Wagle wrote:
> > 
> > I'm trying to upgrade the git that our scripts use, and having the  
> > users modify their paths doesn't work.
> > 
> > Not that horrible to fix some other way, but still a rude thing to  
> > wake up to one day. (ie, today)
> > 
> 
> Did you see the yellow bulldozer coming at your house while brushing your 
> teeth?

That is not a valid point of view when you're a git user, and things
suddenly change from working one day, to not working the next _and_
you don't know why the commands you were using have suddenly vanished.

And there is no documentation seemingly available to tell you what to
use instead.

And the available documentation tells you that the commands you were
using are still there.

And no warnings before hand that the commands you were using were
deprecated.

*That* is what is soo abhorrent about this whole business.

How would you feel if, tomorrow, 'ls', 'tar' etc all gave you "command
not found", 'man ls' still gave you a man page for ls(1) but the
command was now actually called 'listfiles' instead ?

Just put 'alias ls=listfiles' in your .bashrc !

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html