From 4f8ae886d24c3a4560c724eb37b906ae4a4e13be Mon Sep 17 00:00:00 2001 From: "https://launchpad.net/~r0lf" Date: Sat, 24 Apr 2021 10:38:37 +0000 Subject: [PATCH] Added a comment --- ..._2_0bd3de64bc820e002bbbddc88e8095bd._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/bugs/poor_choice_of_name_for_adjusted_branches/comment_2_0bd3de64bc820e002bbbddc88e8095bd._comment diff --git a/doc/bugs/poor_choice_of_name_for_adjusted_branches/comment_2_0bd3de64bc820e002bbbddc88e8095bd._comment b/doc/bugs/poor_choice_of_name_for_adjusted_branches/comment_2_0bd3de64bc820e002bbbddc88e8095bd._comment new file mode 100644 index 0000000000..5f77d3c0c5 --- /dev/null +++ b/doc/bugs/poor_choice_of_name_for_adjusted_branches/comment_2_0bd3de64bc820e002bbbddc88e8095bd._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="https://launchpad.net/~r0lf" + nickname="r0lf" + avatar="http://cdn.libravatar.org/avatar/aa82122557e706df7ba83bd1983eb79ef1ba2e51350217850176d4f9a1bb2bc0" + subject="comment 2" + date="2021-04-24T10:38:37Z" + content=""" +Thank you for the explanation. It certainly explains your situation back when you coded this up. I'm not sure I'm convinced it is good justification to keep things the way they are going forward. + +1. The branch names aren't short +2. The branch names aren't clash-free (see my other report) +3. I switch between branches all the time, that's their purpose. + +For #3, I usually rely on either mark-copy'ing the characters off the terminal with the mouse or via bash-completion. Both are broken. + +Isn't it that people aren't using () for branch or filenames precisely because of the problems you will almost certainly run into? +"""]]