login
Header Space

 
 

Re: why is git destructive by default? (i suggest it not be!)

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: David Jeske <jeske@...>
Cc: Avery Pennarun <apenwarr@...>, Nicolas Pitre <nico@...>, <git@...>
Date: Tuesday, June 24, 2008 - 8:21 am

David Jeske wrote:

By the way, reflog (even if expired) would protect you in this
situation; I have checked wrongly that it does not (chronological
vs. reverse chronological order, and not paying attention to
timestamps).


It is very useful command when deleting larger number of files;
I have "alias rm='rm -i'", and confirming every single file quickly
gets annoying.


Example was about "rm -f *", i.e. removing contents of current directory;
you should be careful when doing it, for example if you are in currect
repository.
 
Some older versions of UNIX supposedly could hose every hidden file you own
upwards if you did "rm -rf .*", as they matched '..' (parent directory)
against '.*'.


No.  I almost never login as root, using 'sudo', 'sudo su -', or relying
on applications asking for root credentials if required (for example when
installing new version of git).

Let me guess: no sharp knives in kitchen? ;-P
-- 
Jakub Narebski
Poland
--
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
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: why is git destructive by default? (i suggest it not be!), Jakub Narebski, (Tue Jun 24, 8:21 am)
speck-geostationary