From c908780413824e8639a1bdd88ff62211a8d574ee Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 6 May 2025 11:29:47 -0400 Subject: [PATCH] comment --- ...t_5_e9a78b2c8ed325ccf57c515bb162fc1d._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/forum/whereused__58___--key_other_branches_w__47__o_checkout/comment_5_e9a78b2c8ed325ccf57c515bb162fc1d._comment diff --git a/doc/forum/whereused__58___--key_other_branches_w__47__o_checkout/comment_5_e9a78b2c8ed325ccf57c515bb162fc1d._comment b/doc/forum/whereused__58___--key_other_branches_w__47__o_checkout/comment_5_e9a78b2c8ed325ccf57c515bb162fc1d._comment new file mode 100644 index 0000000000..776cdb167c --- /dev/null +++ b/doc/forum/whereused__58___--key_other_branches_w__47__o_checkout/comment_5_e9a78b2c8ed325ccf57c515bb162fc1d._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 5""" + date="2025-05-06T15:18:51Z" + content=""" +It's fine to have multiple unrelated branches in a repository, I don't +think you're doing anything wrong. + +Currently --historical stops once it finds one use of the key. +I think you are wanting to find all uses by any of your branches? + +Maybe the right option for this use case would be a --branches that +searches each branch for uses of the key and doesn't stop at the first hit. +Perhaps combined with a --refspec= option that takes a wildcard that can be +used to select which branches to search. +"""]]