From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>, "'Jeff King'" <peff@peff.net>
Cc: "'Phil Hord'" <phil.hord@gmail.com>,
"'Christian Couder'" <christian.couder@gmail.com>,
"'Git'" <git@vger.kernel.org>
Subject: RE: What's cooking in git.git (Jul 2019, #06; Thu, 25)
Date: Mon, 12 Aug 2019 09:39:50 -0400 [thread overview]
Message-ID: <003201d55113$6d4c8ee0$47e5aca0$@nexbridge.com> (raw)
In-Reply-To: <xmqqwofjb4k4.fsf@gitster-ct.c.googlers.com>
On August 11, 2019 8:39 PM, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > IMHO scripting around "action" commands like checkout is less bad than
> > around "output" commands like log. The general action of "switch to
> > this branch" is unlikely to be changed much over the years (or via
> > config), but the output of log, etc, is.
> >
> > There are no guarantees, of course, but I imagine that the tradeoff in
> > simplicity of using git-switch versus manually reimplementing it is
> > probably a good one for many scripts.
>
> Another reason why scripting around "action" may be OK is that most of the
> time scriptors would want to (blindly) adopt improvements made to the
> underly ing command anyway. If you scripted around "git checkout" before
> we introduced multiple worktree feature where a branch that is already
> active in another worktree is protected from getting checked out elsewhere,
> your script will automatically get that protection (and more importantly, the
> error message given as an explanation to the end users) for free. Of course
> your script must be prepared to react correctly to a failure from "git
> checkout", but that goes without saying for any command you invoke in your
> script.
That would describe my subcommunity pretty accurately 😉
Thanks,
Randall
next prev parent reply other threads:[~2019-08-12 13:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 0:19 What's cooking in git.git (Jul 2019, #06; Thu, 25) Junio C Hamano
2019-07-26 14:33 ` Johannes Schindelin
2019-07-26 20:23 ` Junio C Hamano
2019-07-27 19:38 ` Rohit Ashiwal
2019-07-27 20:40 ` Elijah Newren
2019-07-27 20:57 ` Rohit Ashiwal
2019-07-27 21:42 ` Elijah Newren
2019-07-28 20:34 ` Carlo Arenas
2019-08-09 0:13 ` Taylor Blau
2019-08-09 1:34 ` Ariadne Conill
2019-08-09 2:07 ` Taylor Blau
2019-08-09 3:04 ` Ariadne Conill
2019-08-09 3:07 ` Phil Hord
2019-08-09 3:21 ` Ariadne Conill
2019-08-09 11:21 ` Taylor Blau
2019-08-09 11:41 ` Jeff King
2019-08-09 17:39 ` Phil Hord
2019-08-09 14:06 ` Randall S. Becker
2019-08-09 16:29 ` Jeff King
2019-08-09 16:32 ` Randall S. Becker
2019-08-09 17:45 ` Junio C Hamano
2019-08-09 18:05 ` Phil Hord
2019-08-10 6:10 ` Jeff King
2019-08-12 0:39 ` Junio C Hamano
2019-08-12 13:39 ` Randall S. Becker [this message]
2019-08-09 17:44 ` Junio C Hamano
2019-08-09 19:06 ` Randall S. Becker
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='003201d55113$6d4c8ee0$47e5aca0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=phil.hord@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).