From: Oleg Nesterov <oleg@redhat.com>
To: Alexey Gladkov <gladkov.alexey@gmail.com>
Cc: "Luc Van Oostenryck" <luc.vanoostenryck@gmail.com>,
"Uwe Kleine-König / sparse"
<gitlab+9b7df497d06cab14c2bf3c1022d8ca15@salsa.debian.org>,
linux-sparse@vger.kernel.org
Subject: Re: sparse | upgrade to upstream v0.6.2 (!2)
Date: Tue, 4 Aug 2020 20:52:00 +0200 [thread overview]
Message-ID: <20200804185159.GA26829@redhat.com> (raw)
In-Reply-To: <20200804163812.l2njaeyo7fcsbogt@comp-core-i7-2640m-0182e6>
On 08/04, Alexey Gladkov wrote:
>
> Don't get me wrong, I don't mind renaming the utility. This is a good
> short term solution
I think it would be better to rename it in any case, whatever you and Luc
decide. We do not want the naming conflict, imo.
Just in case, I'd personally prefer to keep sindex in sparse's repository,
but of course I won't argue if you guys decide otherwise.
> but to be honest I don't like the name 'sparse-sindex'
> because it is very long.
me too ;)
> Can we think of something shorter ?
I can't. May be just "dissect" ? But I agree in advance with any name.
Oleg.
next prev parent reply other threads:[~2020-08-04 18:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <reply-7f2b156a8ad4ece3334e6b9712c2de05@salsa.debian.org>
[not found] ` <merge_request_28506@salsa.debian.org>
[not found] ` <note_184887@salsa.debian.org>
2020-08-01 16:54 ` sparse | upgrade to upstream v0.6.2 (!2) Luc Van Oostenryck
[not found] ` <note_185118@salsa.debian.org>
[not found] ` <note_185156@salsa.debian.org>
2020-08-02 21:09 ` Luc Van Oostenryck
[not found] ` <note_185002@salsa.debian.org>
[not found] ` <note_185155@salsa.debian.org>
2020-08-02 21:30 ` Luc Van Oostenryck
2020-08-03 14:53 ` Alexey Gladkov
2020-08-04 16:38 ` Alexey Gladkov
2020-08-04 18:52 ` Oleg Nesterov [this message]
2020-08-04 19:33 ` Luc Van Oostenryck
2020-08-04 20:02 ` Luc Van Oostenryck
2020-08-05 10:16 ` Alexey Gladkov
[not found] ` <note_184882@salsa.debian.org>
2020-08-02 13:29 ` Luc Van Oostenryck
2020-08-09 19:21 ` Luc Van Oostenryck
[not found] <note_185299@salsa.debian.org>
[not found] ` <note_185431@salsa.debian.org>
[not found] ` <note_185453@salsa.debian.org>
[not found] ` <note_185458@salsa.debian.org>
[not found] ` <note_185460@salsa.debian.org>
[not found] ` <note_185461@salsa.debian.org>
[not found] ` <note_185530@salsa.debian.org>
[not found] ` <note_185532@salsa.debian.org>
[not found] ` <20200805110418.iutr56vyewhbqr7v@ltop.local>
[not found] ` <20200805112141.ier2xkhm5sqjtbck@comp-core-i7-2640m-0182e6>
2020-08-05 15:20 ` Luc Van Oostenryck
2020-08-05 15:44 ` Alexey Gladkov
2020-08-05 19:58 ` Luc Van Oostenryck
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=20200804185159.GA26829@redhat.com \
--to=oleg@redhat.com \
--cc=gitlab+9b7df497d06cab14c2bf3c1022d8ca15@salsa.debian.org \
--cc=gladkov.alexey@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox