On 2024-09-18 10:28 a.m., Abel Abraham Camarillo Ojeda wrote:
>
>
> On Wed, Sep 18, 2024 at 8:27 AM Paul Galbraith <paul@galbraiths.ca> wrote:
>
>     On 2024-09-08 9:23 p.m., A Tammy wrote:
>     > On 9/8/24 8:06 PM, Paul Galbraith wrote:
>     >> On 2024-09-03 12:36 p.m., Kirill A. Korinsky wrote:
>     >>> On Tue, 03 Sep 2024 14:40:52 +0200,
>     >>> Paul Galbraith <paul@galbraiths.ca> wrote:
>     >>>> On 2024-09-02 6:17 p.m., Kirill A. Korinsky wrote:
>     >>>>> On Mon, 02 Sep 2024 22:58:25 +0200,
>     >>>>> Paul Galbraith <paul@galbraiths.ca> wrote:
>     >>>>>> On 2024-08-04 6:19 a.m., Kirill A. Korinsky wrote:
>     >>>>>>> I haven't tested it, just make a quick read. Plan to test
>     in soon.
>     >>>>>> Any luck?
>     >>>>>>
>     >>>>> Sorry, I forgot about that.
>     >>>>>
>     >>>>> Just tested and it works.
>     >>>>>
>     >>>> Thanks for confirming, are you Ok with the naming?  I think
>     it makes
>     >>>> sense to consistently rename all the executables, and leave
>     it to the
>     >>>> user to create symlinks to preserve functionality for
>     existing scripts
>     >>>> that are using the original b2 names.
>     >>>>
>     >>> This makes sense.
>     >>>
>     >> Updated with a message explaining the rename of b2 -> backblaze-b2.
>     >> OK to add now?
>     >>
>     > basic operations are working for me, OK aisha
>     >
>     Can this be committed now?
>
>
> afaik, ports in freezed right now. this will need to wait for next 
> release cycle

Ok to add now?