Package: git Version: 1:2.45.2-1 Severity: minor Hi,
please excuse me going through the BTS instead of sending direct mail to the maintainer. The mainainer uses gmail, and gmail doesn't accept mail from smaller sites, including mine, any more. Please consider using a mail provider who is not out to break e-mail completely. But now to my question: /etc/bash_completion.d/git-prompt has commen lanugage suggesting that the handling of git-sh-prompt is going to change somewhere in the future. That was 2012. Where are we going with git-sh-prompt? Am I, as a user, supposed to source /usr/lib/git-core/git-sh-prompt in my shell startup scripts in case the sourcing code in /etc/bash_completion.d/git-prompt will go away in the future? And now the other side of the question: As the sudo maintainer, I'd like to establish a __sudo_ps1 function that returns an "s" when a current sudo invocation is still cached for this shell, so that a user can configure her prompt to change to "s$" instead of "$" if sudo wont ask for a password. I would like to include this in the Debian package and maybe even submit it upstream. And I want to do it in a way that doesn't confuse people, thus using the same mechanism that git does with its well-known __git_ps1 function. Where am I supposed to put my shell snippet? Am I doing it right by putting it in /usr/lib/sudo/sudo-sh-prompt or am I cementing something that you as the git maintainer want to get rid of? Sudo already ships shared objects and a helper binary in /usr/libexec/sudo, so maybe it would also be a good idea ot put the shell snippet there as well? What do you think? Greetings Marc
