Witness the following:
sh-3.2$ mkdir testcase
sh-3.2$ cd testcase
sh-3.2$ sudo touch temp
sh-3.2$ ls -al
total 0
drwxr-xr-x 3 glen staff 102 19 Dec 12:38 .
drwxr-xr-x 12 glen staff 408 19 Dec 12:38 ..
-rw-r--r-- 1 root staff 0 19 Dec 12:38 temp
sh-3.2$ echo nope > temp
sh: temp: Permission denied
sh-3.2$ vim temp
# inside vim
itheivery
# press [ESC]
:wq!
# vim exits
sh-3.2$ ls
I did this (was trying to set an 'self' alias with -v):
git() { if [[ $1 == "commit" ]]; then command git commit -v; else command git "$@"; fi; }
git() { if [[ $1 == "commit" ]]; then command git commit -v; else command git "$@"; fi; }
git() { git commit }; )
git() { git commit; }
git() { git (); }
git() { git(); }
git() { git() }
and now all git commmands hang - no error but no re
Code:
glen@Raring:~$ sudo apt-get update && sudo apt-get upgrade
[sudo] password for glen:
< blah blah blah with no errors >
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information...
As part of my work I regularly commit to git. I have a fabric script that does an interactive commit: git commit -a which shows me which files have changed in nano and then lets me write a commit message.
The problem with this flow is sometimes I need to know what changes I've made inside a file.
Hi all, this is my first mod, i present you my enhanced battery % mod.
Most of my my aliases are of this form: alias p='pwd'
I want to alias git commit so that it does git commit -v
But trying to create an alias with a space gives an error:
$ alias 'git commit'='git commit -v'
-bash: alias: `git commit': invalid alias name
I am trying to access commit history on a remote server on a particular branch and project...if I upload something from my local client I can see the commit history whenever I do git log,I read through the doc@ http://git-scm.com/book/en/Git-Basics-Viewing-the-Commit-History but could not get any substantial information on how to access commit history from a remote server....does anyone have the
When I commit a change to the Ubuntu Subversion, I always get the error below.
~$ sudo svn commit -m "Initial Commit" test.txt --username akira
svn: Commit failed (details follow):
svn: Can't open file '/home/svn/myrepo/db/txn-current-lock': Permission denied
How should I set the permission to the txn-current-lock?
I set the permissions below beforehand.
~$ sudo chown -R taro:subversion myrep
Dot Categories: DeveloperKDE Commit Digest is getting back up to speed!
In this week's KDE Commit-Digest: