From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 447FE1F8C8; Thu, 16 Sep 2021 20:30:53 +0000 (UTC) Date: Thu, 16 Sep 2021 20:30:53 +0000 From: Eric Wong To: Konstantin Ryabitsev Cc: meta@public-inbox.org Subject: Re: mbox support in other software Message-ID: <20210916203053.GA25742@dcvr> References: <20210916073437.GA18469@dcvr> <20210916135921.huvkda6sqnzi7ohs@meerkat.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210916135921.huvkda6sqnzi7ohs@meerkat.local> List-Id: Konstantin Ryabitsev wrote: > On Thu, Sep 16, 2021 at 07:34:37AM +0000, Eric Wong wrote: > > git supports mboxo and mboxrd, nowadays; but it seems like most > > other software only know how to deal with one of the mbox family > > (and mixing software on the same mbox leads to bad things). > > I'm not 100% sure git does the right thing with mboxo, see my tirade here: > https://git.kernel.org/pub/scm/utils/b4/b4.git/commit/?id=4950093c0c3ee71e7045b545626d2b232271cbc8&dt=2 Yeah, I was wrong about git supporting mboxo. IIRC, "mbox" used by git relies on strict "From " line parsing so it looks for something that looks like asctime(3) output. IOW, "mbox" for git does its own weird thing, which also sucks. However, git's "mboxrd" (AFAIK) does the right thing (since I contributed it to git :>)