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
Date: Fri, 18 Oct 2019 19:01:51 +0000 [thread overview]
Message-ID: <20191018190151.bgipdtm4ragkz5ox@dcvr> (raw)
In-Reply-To: <20191018032516.GB29290@dcvr>
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...
next prev parent reply other threads:[~2019-10-18 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 3:25 workflow problems and possible public-inbox solutions Eric Wong
2019-10-18 19:01 ` Eric Wong [this message]
2019-10-18 19:03 ` Konstantin Ryabitsev
2019-10-19 0:29 ` Eric Wong
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191018190151.bgipdtm4ragkz5ox@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
--cc=workflows@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).