aboutsummaryrefslogtreecommitdiff
path: root/graphics/clutter-gtk3
diff options
context:
space:
mode:
authorMathieu Arnold <mat@FreeBSD.org>2021-04-08 15:33:10 +0000
committerMathieu Arnold <mat@FreeBSD.org>2021-04-08 15:46:53 +0000
commitc618b1501762ea9cd7ef0a3ae44cec7970dfbd5c (patch)
treea1188120ba09729292af743dbcf2f851f1fff79f /graphics/clutter-gtk3
parentce196940be576646bf30593d6781df3a0170a947 (diff)
downloadports-c618b1501762ea9cd7ef0a3ae44cec7970dfbd5c.tar.gz
ports-c618b1501762ea9cd7ef0a3ae44cec7970dfbd5c.zip
tindex: Amend last commit a bit.
When you run `git log foo` foo can be, from git-log(1), `[<revision range>] [[--] <path>...]`, so, may things. - A "revision range" described by gitrevision(7) (don't got there unless you have a few hours, or already lost your sanity), which can be : * a commit hash, * a tag * a branch, * a ref name * a "describe output" * and many other ways to describe revisions * a range made by any of the above - An existing path. When it can't find any of those, git figures out that you meant something else and made a typo, and exits. If you really meant a path, you have to run `git log -- foo`. Then git knows that you meant a path and only a path, it will then assume that you knew what you meant, and will go look in the history.
Diffstat (limited to 'graphics/clutter-gtk3')
0 files changed, 0 insertions, 0 deletions