Show changed files with git log
Answer:
In svn, you can use
# svn log -v
to show a detail list of changed files in each commit.
In git, you can use to have similar effect:
# git log --stat
.
Linux Ask! is a Q & A web site specific for Linux related questions. Questions are collected, answered and audited by experienced Linux users.
Show changed files with git log
Answer:
In svn, you can use
# svn log -v
to show a detail list of changed files in each commit.
In git, you can use to have similar effect:
# git log --stat
.
Erase old downloaded packages from apt-get's cache
Answer:
The erase old downloaded packages from apt-get's cache, which are stored under the location: /var/cache/apt/archives
Try:
# sudo apt-get autoclean
Show svn log for a particular folder
Answer:
To show the svn log for a particular folder, just need to use..
# svn log /data/foo
------------------------------------------------------------------------
r1935 | [email protected] | 2011-11-23 19:05:43 +0800 (Wed, 23 Nov 2011) | 1 line
Fixed the crash issue (Jira 2001)
------------------------------------------------------------------------
r1934 | [email protected] | 2011-11-23 18:47:54 +0800 (Wed, 23 Nov 2011) | 1 line
Added missed files
The difference between last and break used in Nginx URL rewrite
Answer:
When you rewrite URL using the Nginx's rewrite directive, you might be confused that what are the exact difference between last and break?
From the official site: http://wiki.nginx.org/HttpRewriteModule#rewrite
last - completes processing of rewrite directives, after which searches for corresponding URI and location
break - completes processing of rewrite directives and breakes location lookup cycle by not doing any location lookup and internal jump at all
So: both directives will end the rewrite cycle, but break will not do any location lookup and internal jump afterward.
Debug Nginx configuration using the echo module
Answer:
When you want to confirm you have configured Nginx correctly, e.g. make sure you have the right rewrite rules. The easiest way is to use the echo module to debug.
E.g.
..
location / {
rewrite ^/foo /bar break;
echo $uri; # try with other variables you want to trace
}
When you use curl to request the page, you should receive something like:
# curl http://example.com/foo
bar