From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.5 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE,RDNS_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 Received: (qmail 10423 invoked from network); 10 Mar 2020 18:10:36 -0000 Received-SPF: pass (minnie.tuhs.org: domain of minnie.tuhs.org designates 45.79.103.53 as permitted sender) receiver=inbox.vuxu.org; client-ip=45.79.103.53 envelope-from= Received: from unknown (HELO minnie.tuhs.org) (45.79.103.53) by inbox.vuxu.org with ESMTP; 10 Mar 2020 18:10:36 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 333A19BC10; Wed, 11 Mar 2020 04:10:34 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id CA1709BB47; Wed, 11 Mar 2020 04:10:20 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="aYjT82e3"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id BE22E9BB47; Wed, 11 Mar 2020 04:10:18 +1000 (AEST) Received: from mail-qt1-f171.google.com (mail-qt1-f171.google.com [209.85.160.171]) by minnie.tuhs.org (Postfix) with ESMTPS id 3C7CE9BB46 for ; Wed, 11 Mar 2020 04:10:18 +1000 (AEST) Received: by mail-qt1-f171.google.com with SMTP id v15so10386446qto.2 for ; Tue, 10 Mar 2020 11:10:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Iscn96AfhhGgKcZ+1ozUi6zlIKmSEzSs0hM91Tb2GWE=; b=aYjT82e3dMz4KP/7RkjaSMW0e/7wY1s6DinK/cqkw/YmJWBNuf10uEMWgEG7ifgsST oPQvrl1ybkPGArZaWw78gBRcw+rB62yi3eWxVs+dNeS8ZrUOX6qtljo4vDdLw5uk5QQm A4mdxWnjO6/bTNolSTNOVblgZWgnNCpEprIF5tvuFX1HGijetfrdjQfDnUNmIbqea0JS ekvqWEUMAdvVEsS1pjt/XvVoWJXwgyAMFN/bd7GpPAtLH0KG8Ff/VWD3NtFq3VxqHGt1 ypENNYvv2oMwGFAQv8SRh4LiVVO2imlCsl+xzFtrpTXrSLzLb7cr10zFAzlddffTKgUS lhRg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Iscn96AfhhGgKcZ+1ozUi6zlIKmSEzSs0hM91Tb2GWE=; b=UoiycGP/VG5D9ohQyG1BEkMQ0bupYiJSLA4IW202NbOnXbG9XNZLHASqSDHrZI5kRC N9iq+JiWiBbzE1C0nMgE6mkJSdmNEKqJrVC/8LEKUxazE7MwGZwu1yI2Jfyh6UU5nJYT /STKZxvRI5dj8RUswHXhJShKoqm3m1tIS0pd2uGSBVHuoV97dBWO6VclyyIkuS7DTUKG FafQWvALBLsXV2REDy2HXe86JQUdAixZhphbgITQlKk6BQJjZ3FOKe11abTxCPuD2kEK 3//V2blu5jC37yqsVUQchBp2pcaG129PrxEA+QgaBu2mLZhRw03YffnAzJLhp+qBD5rO VixQ== X-Gm-Message-State: ANhLgQ1+MvrEFTYzdMc85LJLcEfMqJsOBPhkAHWH6cGioRsPC7145kB8 pCttb/wSoTOVmQsqlz5JHWwQcIW/NRti/0ZJy9E= X-Google-Smtp-Source: ADFU+vvaEREv0fuzZ5j8FpMCTHXagihCEviWFxPwZ5vlEl5zEKV4tYtSolOyMtvHoqpHIrEoFeRHL8Gqkq1xZNn1Frw= X-Received: by 2002:ac8:7b8e:: with SMTP id p14mr19840835qtu.352.1583863816222; Tue, 10 Mar 2020 11:10:16 -0700 (PDT) MIME-Version: 1.0 References: <202003101615.02AGFLgS075920@coolidge.cs.dartmouth.edu> <20200310174440.00B20156E45D@mail.bitblocks.com> In-Reply-To: <20200310174440.00B20156E45D@mail.bitblocks.com> From: Dan Cross Date: Tue, 10 Mar 2020 14:09:39 -0400 Message-ID: To: Bakul Shah Content-Type: multipart/alternative; boundary="000000000000237db605a0840875" Subject: Re: [TUHS] Command line options and complexity X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: The Eunuchs Hysterical Society , Doug McIlroy Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000237db605a0840875 Content-Type: text/plain; charset="UTF-8" On Tue, Mar 10, 2020 at 1:44 PM Bakul Shah wrote: > On Tue, 10 Mar 2020 13:38:23 -0400 Dan Cross wrote: > > > > This begs questions of stability: in the event of non-unique keys and > > non-key fields in the sortable data, which "records" (lines) are kept and > > which are discarded? Surely the "first" is kept and subsequent entries > with > > the same key suppressed, but I confess I don't know enough about the > > internals of sed to know even what algorithm it uses (I assume a > disk-based > > merge sort?), but I would imagine these details have changed over time. > > FreeBSD manpage for sort says that -u implies a stable sort, > similar to -s. > Thanks; that makes sense. I'm still interested in historical data, though. :-) - Dan C. --000000000000237db605a0840875 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Mar 10, 2020 at 1:44 PM Bakul Sha= h <bakul@bitblocks.com> wr= ote:
On Tue, 10 Mar 2020 13:38:23 -0400 Dan Cross <crossd@gmail.com> wrote:=
>
> This begs questions of stability: in the event of non-unique keys and<= br> > non-key fields in the sortable data, which "records" (lines)= are kept and
> which are discarded? Surely the "first" is kept and subseque= nt entries with
> the same key suppressed, but I confess I don't know enough about t= he
> internals of sed to know even what algorithm it uses (I assume a disk-= based
> merge sort?), but I would imagine these details have changed over time= .

FreeBSD manpage for sort says that -u implies a stable sort,
similar to -s.

Thanks; that makes sense= . I'm still interested in historical data, though. :-)

=C2=A0 =C2=A0 =C2=A0 =C2=A0 - Dan C.
=C2=A0
<= /div> --000000000000237db605a0840875--