Tarantool development patches archive
 help / color / mirror / Atom feed
From: Sergey Bronnikov via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Alexander Turenko <alexander.turenko@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH] tools: implement toolchain for crash artefacts
Date: Thu, 25 Mar 2021 12:45:21 +0300	[thread overview]
Message-ID: <0230f8b4-055e-9fb3-ce06-20ffbfcce8f8@tarantool.org> (raw)
In-Reply-To: <20210324202529.v3cky77ky6tgd6x2@tkn_work_nb>

Hello,

On 24.03.2021 23:25, Alexander Turenko wrote:
>> 1. in a private conversation we decided to remove mention of public resource
>> in a message "http://transfer.sh".
> Can you (or Igor) share a reason?

We suppose that coredump may contain a sensitive data

and it would be wrong to recommend to share an archive on a public file 
hosting (at least without encryption).

>>   TOOL=$(basename "$0")
>> +#TOOLPATH="$( cd -- "$(dirname "$0")" >/dev/null 2>&1 ; pwd -P )"
>> +TOOLPATH=$(realpath -s $0)
> 'realpath' is not necessarily available. Actually I saw that it may be
> not available on Mac OS, but I didn't saw such situation on Linux.
> However realpath from busybox does not support -s option (verified on
> Alpine 3.10).
>
> My opinion: it is better to don't extend the list of external
> dependencies in this case.
>
> I would also highlight that it is quite usual to use just $0 in a usage
> message:
>
>   | $ cat --help | head -n 1
>   | Usage: cat [OPTION]... [FILE]...
>   |
>   | $ /bin/cat --help | head -n 1
>   | Usage: /bin/cat [OPTION]... [FILE]...

  reply	other threads:[~2021-03-25  9:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 13:23 Igor Munkin via Tarantool-patches
2021-03-03 12:44 ` Sergey Bronnikov via Tarantool-patches
2021-03-08  4:56   ` Alexander Turenko via Tarantool-patches
2021-03-08 11:54     ` Sergey Bronnikov via Tarantool-patches
2021-03-11 12:13   ` Igor Munkin via Tarantool-patches
2021-03-24 16:02     ` Sergey Bronnikov via Tarantool-patches
2021-03-24 20:25       ` Alexander Turenko via Tarantool-patches
2021-03-25  9:45         ` Sergey Bronnikov via Tarantool-patches [this message]
2021-04-19 21:06       ` Igor Munkin via Tarantool-patches
2021-03-15 16:30 ` Alexander Turenko via Tarantool-patches
2021-04-19 20:42   ` Igor Munkin via Tarantool-patches
2021-04-19 23:57     ` Alexander Turenko via Tarantool-patches
2021-04-20 12:14       ` Igor Munkin via Tarantool-patches
2021-04-19 22:51 ` Igor Munkin via Tarantool-patches

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=0230f8b4-055e-9fb3-ce06-20ffbfcce8f8@tarantool.org \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=alexander.turenko@tarantool.org \
    --cc=sergeyb@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH] tools: implement toolchain for crash artefacts' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox