|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
I think the request is infeasible, unless we provide a "command line arguments" field for every git command we invoke, in every context where it is invoked.
For example, the current git commands used by the plugin include:
Those commands are used in specific contexts, with some used in multiple contexts. I don't see how we could represent a user interface to the user which would describe the location of the usage, without fully describing the details of that usage so that they knew the context. The user interface to allow command line control of each of those contexts is much more work and much more difficult to explain to users than the current, simplified model.