From 9192e0a28d1ed662c201fa77b43970aec326796c Mon Sep 17 00:00:00 2001 From: Nick Craig-Wood Date: Wed, 5 Oct 2016 14:35:23 +0100 Subject: [PATCH] Link to git log from beta downloads --- docs/content/downloads.md | 7 ++++--- docs/content/downloads.md.in | 7 ++++--- 2 files changed, 8 insertions(+), 6 deletions(-) diff --git a/docs/content/downloads.md b/docs/content/downloads.md index 5122f5474..0164a5c3e 100644 --- a/docs/content/downloads.md +++ b/docs/content/downloads.md @@ -45,9 +45,10 @@ to master. Note these are named like {Version Tag}-{Commit Number}-g{Git Commit Hash} -You can match the `Git Commit Hash` up with `git log`. The most -recent release will have the largest `Version Tag` and `Commit Number` -and will normally be at the end of the list. +You can match the `Git Commit Hash` up with the [git +log](https://github.com/ncw/rclone/commits/master). The most recent +release will have the largest `Version Tag` and `Commit Number` and +will normally be at the end of the list. The beta releases haven't been through the full integration test suite like the releases. However it is useful to try the latest beta before diff --git a/docs/content/downloads.md.in b/docs/content/downloads.md.in index 08d66506d..62b3105bd 100644 --- a/docs/content/downloads.md.in +++ b/docs/content/downloads.md.in @@ -46,9 +46,10 @@ to master. Note these are named like {Version Tag}-{Commit Number}-g{Git Commit Hash} -You can match the `Git Commit Hash` up with `git log`. The most -recent release will have the largest `Version Tag` and `Commit Number` -and will normally be at the end of the list. +You can match the `Git Commit Hash` up with the [git +log](https://github.com/ncw/rclone/commits/master). The most recent +release will have the largest `Version Tag` and `Commit Number` and +will normally be at the end of the list. The beta releases haven't been through the full integration test suite like the releases. However it is useful to try the latest beta before