From: Junio C Hamano <gitster@pobox•com>
To: "Torsten Bögershausen" <tboegi@web•de>
Cc: Beat Bolli <dev+git@drbeat•li>, git@vger•kernel.org
Subject: Re: [PATCH 1/3] update_unicode.sh: update the uniset repo if it exists
Date: Mon, 12 Dec 2016 22:42:22 -0800 [thread overview]
Message-ID: <xmqq37hs72k1.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <d91b5e69-9b90-e21e-0dcb-8eace00ddd74@web.de> ("Torsten Bögershausen"'s message of "Tue, 13 Dec 2016 07:16:26 +0100")
Torsten Bögershausen <tboegi@web•de> writes:
> The typical instructions I have seen are a sequence of shell commands
> to be executed, which hopefully simply work by doing "copy-and-paste".
> I find this error-prone, as you you may loose the last character while
> moving the mouse, or don't check the error message or return codes.
> Having a pre-baked shell script, which does use "&&" is in that way
> more attractive,
> and the README can be as simple as run "update-unicode.sh" and that's it.
That's OK as well.
> "contrib/uniwidth/" may be different to find, how about contrib/update-unicode ?
This, too. And as long as .gitignore pattern is set up correctly
there, I do not think we terribly mind "git clone ..from..there.."
into it, either.
next prev parent reply other threads:[~2016-12-13 6:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 23:34 [PATCH 1/3] update_unicode.sh: update the uniset repo if it exists Beat Bolli
2016-12-11 23:34 ` [PATCH 2/3] update_unicode.sh: remove the plane filters Beat Bolli
2016-12-11 23:34 ` [PATCH 3/3] update_unicode.sh: restore hexadecimal output Beat Bolli
2016-12-12 5:53 ` [PATCH 1/3] update_unicode.sh: update the uniset repo if it exists Torsten Bögershausen
2016-12-12 8:54 ` Beat Bolli
2016-12-12 18:12 ` Torsten Bögershausen
2016-12-12 18:33 ` Junio C Hamano
2016-12-12 23:50 ` Beat Bolli
2016-12-13 6:16 ` Torsten Bögershausen
2016-12-13 6:42 ` Junio C Hamano [this message]
2016-12-12 19:24 ` Beat Bolli
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq37hs72k1.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=dev+git@drbeat$(echo .)li \
--cc=git@vger$(echo .)kernel.org \
--cc=tboegi@web$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox