From: Philippe Blain <levraiphilippeblain@gmail.com>
To: tools@linux.kernel.org
Cc: konstantin@linuxfoundation.org
Subject: [PATCH b4 0/4] Add the man page to the pip package
Date: Thu, 12 Nov 2020 10:21:30 -0500 [thread overview]
Message-ID: <20201112152134.96498-1-levraiphilippeblain@gmail.com> (raw)
Hi ! I'm a Git contributor and just discovered b4 yesterday.
I'm already convinced it will be a great addition to my workflow.
I noticed that the man page is not installed when you 'pip install' the
package, so patch 4/4 in this here series takes care of that.
The other 3 patches are project-level goodies that I thought were good
additions. Feel free to drop them if you don't think so.
Cheers!
Philippe.
P.S. a quick search on https://lore.kernel.org/git/ reveals you did not
formally announce neither b4 nor its predecessor get-lore-mbox there. I think
it could be helpful for some Git folks too :)
Philippe Blain (4):
Add '.venv' to .gitignore
Link to the README from PyPI
Add pointers to https://linux.kernel.org/g/tools
Distribute the manpage with the pip package
.gitignore | 1 +
README.rst | 3 ++-
man/b4.5 | 3 ++-
man/b4.5.rst | 3 ++-
setup.py | 6 +++++-
5 files changed, 12 insertions(+), 4 deletions(-)
base-commit: f33033c03cf96ed769289ebf6d3c26b0cf540683
--
2.27.0
next reply other threads:[~2020-11-12 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 15:21 Philippe Blain [this message]
2020-11-12 15:21 ` [PATCH b4 1/4] Add '.venv' to .gitignore Philippe Blain
2020-11-12 15:21 ` [PATCH b4 2/4] Link to the README from PyPI Philippe Blain
2020-11-12 15:21 ` [PATCH b4 3/4] Add pointers to https://linux.kernel.org/g/tools Philippe Blain
2020-11-12 15:21 ` [PATCH b4 4/4] Distribute the manpage with the pip package Philippe Blain
2020-11-17 21:05 ` [PATCH b4 0/4] Add the man page to " Konstantin Ryabitsev
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201112152134.96498-1-levraiphilippeblain@gmail.com \
--to=levraiphilippeblain@gmail.com \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.