On Fri, Dec 16, 2022 at 2:06 AM Junio C Hamano <gitster@xxxxxxxxx> wrote: > > People usually make changes to the system to make it "more useful" > and/or "more helpful", and almost never to make it "less helpful". > Phrases you would use to explain why the failures become more > helpful with this change (compared to without) would help to promote > it in the "git shortlog --no-merges" output for the next release. > E.g. "make X failures stand out more", "make X failures gramatically > correct", "show X failures more concisely", etc. I will resend with a hopefully better explanation. > directory? Shouldn't this hunk be a separate topic on its own, > or at least a separate patch on its own in the series? It will now be a separate patch. > Is it safe to assume we run Bash here, or can GitHub start using > other shells that lack the Bash-ism shell arrays and we should > protect against such future? > > I suspect that we are already depend on <<< Bash-ism, so one more > dependency to Bash-ism is not a problem here? I dunno. While GitHub could probably allow other shells to be used, changing the default would probably break a lot of things at this point. Thanks for the feedback, ...chris.
