From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
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 E67381F4C0;
	Fri, 18 Oct 2019 19:01:51 +0000 (UTC)
Date: Fri, 18 Oct 2019 19:01:51 +0000
From: Eric Wong <e@80x24.org>
To: workflows@vger.kernel.org
Cc: meta@public-inbox.org
Subject: Re: workflow problems and possible public-inbox solutions
Message-ID: <20191018190151.bgipdtm4ragkz5ox@dcvr>
References: <20191018032516.GB29290@dcvr>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20191018032516.GB29290@dcvr>
List-Id: <meta.public-inbox.org>

Eric Wong <e@80x24.org> wrote:
> Maybe some other stuff, too (feel free to add)

Ease-of-use is another...  I was an early adopter of git
and a user of tla (GNU arch) before that, which probably
makes me too numb to deal with this matter :P

Perhaps web UIs which tells users about command-line tools would
be helpful.

Linking to the git-send-email(1) manpage is one example of
that in public-inbox (but IMHO not as important as informing
users about Message-IDs).

Pointers to inform casual readers which tools (e.g. git
request-pull, git format-patch) were used to generate certain
emails could be useful, too...  I remember being asked how I
generated my request pull emails to a low-key project several
years ago, at least...