aboutsummaryrefslogtreecommitdiffstats
path: root/references.go
diff options
context:
space:
mode:
authorMáximo Cuadros <mcuadros@gmail.com>2016-02-16 17:31:09 +0100
committerMáximo Cuadros <mcuadros@gmail.com>2016-02-16 17:37:29 +0100
commit1931dfbf38508e790e9f129873bc073aacc6a50f (patch)
treef57f34d75a73ca5f7bab800f5c8510f96522b686 /references.go
parentdd8e9b02df17639b625b8c9c03f9537f5cfc039c (diff)
downloadgo-git-1931dfbf38508e790e9f129873bc073aacc6a50f.tar.gz
remove package docv2.2.0
Diffstat (limited to 'references.go')
-rw-r--r--references.go17
1 files changed, 0 insertions, 17 deletions
diff --git a/references.go b/references.go
index 0c57df9..c69917d 100644
--- a/references.go
+++ b/references.go
@@ -1,20 +1,3 @@
-// Package revlist allows to create the revision history of a file, this
-// is, the list of commits in the past that affect the file.
-//
-// The general idea is to traverse the git commit graph backward,
-// flattening the graph into a linear history, and skipping commits that
-// are irrelevant for the particular file.
-//
-// There is no single answer for this operation. The git command
-// "git-revlist" returns different histories depending on its arguments
-// and some internal heuristics.
-//
-// The current implementation tries to get something similar to what you
-// whould get using git-revlist. See the failing tests for some
-// insight about how the current implementation and git-revlist differs.
-//
-// Another way to get the revision history for a file is:
-// git log --follow -p -- file
package git
import (