Re: Support for --stdin-paths in commit, add, etc
- From
- Alexandr Miloslavskiy <alexandr.miloslavskiy@syntevo.com>
- Date
- Aug 1, 2019, 20:40 UTC
- Message-ID
- <27220d22-8c9a-dda2-764b-709dcd85d788@syntevo.com>
- In-Reply-To
- <xmqqmugsmy2e.fsf@gitster-ct.c.googlers.com>
On 01.08.2019 22:26, Junio C Hamano wrote:
> All true. Perhaps we need a separate tutorial for scripters to > teach them how to properly combine the plumbing commands?
@Phillip thanks for your effort!
However, I must admit that for us, this cure is worse then the problem.
We're not exactly scripting, rather we're assisting users to make their work with git more convenient/efficient. If we replace all the familiar commands with exotic combinations of 2-3 chained plumbing, this will definitely leave most users completely clueless about what our UI is doing (we have a window that shows all executed commands).
On top of that, I think that my quick analysis only uncovered like 1/3 of all the new edge cases (compared to using high-level commands) and the solutions already look quite scary to me. Taking the other 2/3 into account, it really feels that this would be a path of lots of pain and many bugfixes.