discussion and development of piem
 help / color / mirror / code / Atom feed
blob 4dd52f983e766a40854307cb00afa79238343eb2 1715 bytes (raw)
name: README 	 # note: path name is non-authoritative(*)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
 

piem --- Emacs tools and glue for working with public-inbox archives
====================================================================

This project is currently in the early stages of development.  In
general, anything that relates to interacting with public-inbox
(https://public-inbox.org/README) archives from Emacs is worth
considering, at least at this point.

Much of the current functionality focuses on mapping public-inbox
endpoints (email, nntp, http, rss) to associated code repositories in
order to apply patches, including integration with b4-am to extract
and process patches (https://git.kernel.org/pub/scm/utils/b4/b4.git).
Upcoming development will largely focus on extending the very basic
support public-inbox's local email interface (lei).

Documentation is available online at

    https://docs.kyleam.com/piem/

Bug reports, patches, questions, and other feedback are welcome.
Please send a plain-text email to

    piem@inbox.kyleam.com

Messages that include this address are public and available as
public-inbox archives at

    https://inbox.kyleam.com/piem/


Related projects
----------------

If you're interested in applying patches but aren't working with a
public-inbox instance, it's still possible to use piem (see the
documentation).  However, in this case, you may want to consider
mailscripts (https://git.spwhitton.name/mailscripts/), a "collection
of scripts for manipulating e-mail on Debian".  Its
notmuch-extract-patch script (accessible via Emacs commands) provides
an alternative to b4 for extracting a patch series from a thread.

And if you're searching for an Emacs interface for *sending* patches,
take a look at git-email (https://sr.ht/~yoctocell/git-email/).

debug log:

solving 4dd52f98 ...
found 4dd52f98 in https://git.kyleam.com/piem/

(*) Git path names are given by the tree(s) the blob belongs to.
    Blobs themselves have no identifier aside from the hash of its contents.^

Code repositories for project(s) associated with this public inbox

	https://git.kyleam.com/piem/

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).