summaryrefslogtreecommitdiff
path: root/file
diff options
context:
space:
mode:
Diffstat (limited to 'file')
-rw-r--r--file/git-hist.c5
-rw-r--r--file/git-hist.h2
2 files changed, 3 insertions, 4 deletions
diff --git a/file/git-hist.c b/file/git-hist.c
index 4b81ce8..62d1f01 100644
--- a/file/git-hist.c
+++ b/file/git-hist.c
@@ -37,7 +37,6 @@
struct branch {
const char *name;
git_commit *commit;
-
};
struct vcs_history {
@@ -373,7 +372,7 @@ static char *append(char *s, char *add)
/*
* @@@ This one is a bit inconvenient. It depends both on the information the
* VCS provides, some of which is fairly generic, but some may not be, and
- * the very specific constraints imposed by the markup format of Pango.
+ * the very specific constraints imposed by the markup format of Pango.
*/
char *vcs_git_long_for_pango(struct vcs_hist *h,
@@ -676,7 +675,7 @@ void hist_iterate(struct vcs_history *history,
/* @@@ still haven't tested -+- */
-
+
//#define DEBUG
// http://stackoverflow.com/questions/12132862/how-do-i-get-the-name-of-the-current-branch-in-libgit2
diff --git a/file/git-hist.h b/file/git-hist.h
index c5b7045..58cb7eb 100644
--- a/file/git-hist.h
+++ b/file/git-hist.h
@@ -21,7 +21,7 @@
enum thread {
thread_none = 0,
thread_self = 1 << 0, /* -o- */
- thread_newer = 1 << 1, /* -'- or -+- */
+ thread_newer = 1 << 1, /* -'- or -+- */
thread_older = 1 << 2, /* -.- or -+- */
thread_other = 1 << 3, /* -|- or -+- */
};