{"thread":{"id":"4227","subject":"[PATCH] Reference git-check-ref-format in git-branch.","startedAt":"2006-05-21T01:54:46Z","lastAt":"2006-05-21T09:07:05Z","messageCount":2,"participants":["Shawn Pearce","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"20366","messageId":"20060521015446.GA7605@spearce.org","threadId":"4227","inReplyTo":null,"subject":"[PATCH] Reference git-check-ref-format in git-branch.","fromName":"Shawn Pearce","fromEmail":"spearce@spearce.org","sentAt":"2006-05-21T01:54:46Z","receivedAt":"2006-05-21T01:54:46Z","isPatch":true,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Its nice to have git-check-ref-format actually get mentioned in\ngit-branch's documentation as the syntax of a ref name must conform\nto what is described in git-check-ref-format.\n\nSigned-off-by: Shawn O. Pearce <spearce@spearce.org>\n\n---\n Sorry about this patch being built on pu.  It clearly has no\n relationship to current pu, but the new -l appears in the hunk\n below...\n\n1e2080dcf2f8e76e0fcf48684e5c6b182f695e0a\n Documentation/git-branch.txt   |    3 +++\n Documentation/git-checkout.txt |    5 ++++-\n 2 files changed, 7 insertions(+), 1 deletions(-)\n\n1e2080dcf2f8e76e0fcf48684e5c6b182f695e0a\ndiff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt\nindex a7bec3c..d43ef1d 100644\n--- a/Documentation/git-branch.txt\n+++ b/Documentation/git-branch.txt\n@@ -49,6 +49,9 @@ OPTIONS\n \n <branchname>::\n \tThe name of the branch to create or delete.\n+\tThe new branch name must pass all checks defined by\n+\tgitlink:git-check-ref-format[1].  Some of these checks\n+\tmay restrict the characters allowed in a branch name.\n \n <start-point>::\n \tThe new branch will be created with a HEAD equal to this.  It may\ndiff --git a/Documentation/git-checkout.txt b/Documentation/git-checkout.txt\nindex 0643943..fbdbadc 100644\n--- a/Documentation/git-checkout.txt\n+++ b/Documentation/git-checkout.txt\n@@ -35,7 +35,10 @@ OPTIONS\n \tForce a re-read of everything.\n \n -b::\n-\tCreate a new branch and start it at <branch>.\n+\tCreate a new branch named <new_branch> and start it at\n+\t<branch>.  The new branch name must pass all checks defined\n+\tby gitlink:git-check-ref-format[1].  Some of these checks\n+\tmay restrict the characters allowed in a branch name.\n \n -l::\n \tCreate the new branch's ref log.  This activates recording of\n-- \n1.3.3.gfad60\n"},{"id":"20386","messageId":"7vhd3jzqyu.fsf@assigned-by-dhcp.cox.net","threadId":"4227","inReplyTo":"20060521015446.GA7605@spearce.org","subject":"Re: [PATCH] Reference git-check-ref-format in git-branch.","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-05-21T09:07:05Z","receivedAt":"2006-05-21T09:07:05Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Shawn Pearce <spearce@spearce.org> writes:\n\n>  Sorry about this patch being built on pu.  It clearly has no\n>  relationship to current pu, but the new -l appears in the hunk\n>  below...\n\n\"am -3 -s -u\" is how I handle patches anyway, and it did not\nhave much trouble backporting it to the tip of \"master\".\n"}]}