From 9d71dbc5b87a1fc13280efff068ef8fd323ec762 Mon Sep 17 00:00:00 2001
From: Boris Kolpackov <boris@codesynthesis.com>
Date: Tue, 13 Feb 2018 13:48:28 +0200
Subject: Respec git repository URL fragment format

---
 bpkg/rep-add.cli | 20 +++++++++++++-------
 1 file changed, 13 insertions(+), 7 deletions(-)

(limited to 'bpkg/rep-add.cli')

diff --git a/bpkg/rep-add.cli b/bpkg/rep-add.cli
index 7f9bb09..2a4210d 100644
--- a/bpkg/rep-add.cli
+++ b/bpkg/rep-add.cli
@@ -57,19 +57,25 @@ namespace bpkg
      \
      #<tag>
      #<branch>
-     #[<branch>]@<commit-id>
+     #<commit-id>
+     #<branch>@<commit-id>
      \
 
-     In the last form <branch> is optional and is only used to minimize the
-     amount of data to fetch. If specified, then the commit must belong to its
-     history. Note also that no abbreviated commit ids are supported and
-     <commit-id> must be the complete, 40-character SHA1 string. Below are
-     some examples of git repository URLs:
+     In the last form <branch> is only used to minimize the amount of data to
+     fetch. If specified, then the commit must belong to its history.
+
+     No abbreviated commit ids are supported and <commit-id> must be the
+     complete, 40-characters SHA1 string. A 40-characters fragment that
+     consists of only hexadecimal digits is assumed to be a commit id and a
+     branch/tag otherwise. In an unlikely case this produces an incorrect
+     result, the last form with omitted <commit-id> can be used.
+
+     Below are some examples of git repository URLs:
 
      \
      https://example.com/foo.git#v1.2.3
      https://example.com/foo.git#master
-     https://example.com/foo.git#@48fba3625d65941bb85a39061bcf795d4949c778
+     https://example.com/foo.git#48fba3625d65941bb85a39061bcf795d4949c778
      https://example.com/foo.git#bar@48fba3625d65941bb85a39061bcf795d4949c778
      \
 
-- 
cgit v1.1