From: Alexandr Miloslavskiy <alexandr.miloslavskiy@syntevo.com>
To: Junio C Hamano <gitster@pobox.com>,
Phillip Wood <phillip.wood123@gmail.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: Support for --stdin-paths in commit, add, etc
Date: Thu, 1 Aug 2019 22:40:23 +0200 [thread overview]
Message-ID: <27220d22-8c9a-dda2-764b-709dcd85d788@syntevo.com> (raw)
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.
next prev parent reply other threads:[~2019-08-01 20:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 15:45 Support for --stdin-paths in commit, add, etc Alexandr Miloslavskiy
2019-07-31 17:15 ` Junio C Hamano
2019-07-31 17:19 ` Jeff King
2019-07-31 21:21 ` Junio C Hamano
2019-08-01 13:25 ` Alexandr Miloslavskiy
2019-08-01 17:35 ` Phillip Wood
2019-08-01 20:26 ` Junio C Hamano
2019-08-01 20:40 ` Alexandr Miloslavskiy [this message]
2019-08-02 11:33 ` Johannes Schindelin
2019-08-02 11:45 ` Alexandr Miloslavskiy
2019-08-02 14:48 ` Johannes Schindelin
2019-08-02 14:52 ` Alexandr Miloslavskiy
2019-08-02 11:52 ` Alexandr Miloslavskiy
2019-08-02 14:47 ` Johannes Schindelin
2019-08-02 15:11 ` Alexandr Miloslavskiy
2019-08-01 14:26 ` René Scharfe
2019-08-01 14:33 ` Alexandr Miloslavskiy
2019-08-01 15:56 ` Junio C Hamano
2019-08-01 16:04 ` Alexandr Miloslavskiy
2019-08-01 20:45 ` Junio C Hamano
2019-08-01 20:51 ` Alexandr Miloslavskiy
2019-08-02 11:40 ` Johannes Schindelin
2019-08-02 11:44 ` Alexandr Miloslavskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27220d22-8c9a-dda2-764b-709dcd85d788@syntevo.com \
--to=alexandr.miloslavskiy@syntevo.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=phillip.wood123@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).