Philadelphia, PA
I write code.
From Drew DeVault to ~sircmpwn/aerc
Thanks! To git.sr.ht:~sircmpwn/aerc 61c94e5..ccf5c02 master -> master
From Drew DeVault to ~sircmpwn/sr.ht-dev
This does not appear to solve the problem: Error: clone repository git@git.sr.ht:~sircmpwn/scdoc: parse git@git.sr.ht:~sircmpwn/scdoc: first path segment in URL cannot contain colon Did you test this patch?
From Drew DeVault to ~sircmpwn/aerc
Looks great, thanks! To git.sr.ht:~sircmpwn/aerc 198661b..61c94e5 master -> master
From Drew DeVault to ~sircmpwn/sr.ht-dev
This LGTM. Can you get these applied, Ludovic?
From Drew DeVault to ~sircmpwn/sr.ht-dev
Thanks! To git.sr.ht:~sircmpwn/git.sr.ht abcd048..0aca4c9 master -> master * [new tag] 0.28.12 -> 0.28.12
From Drew DeVault to ~sircmpwn/sr.ht-dev
Thanks! To git.sr.ht:~sircmpwn/scm.sr.ht 3028440..18b69c7 master -> master * [new tag] 0.12.3 -> 0.12.3
From Drew DeVault to ~sircmpwn/sr.ht-admins
Administrators of sr.ht installations on Arch Linux will need to use the new key to continue receiving package updates. The new key can be obtained like so: pacman-key --recv-keys C0AAFC1676BD998617C94C42DC59670F1EB0A189 pacman-key --lsign-key C0AAFC1676BD998617C94C42DC59670F1EB0A189 These commands must be run as root. If your keyserver has not yet received the new key, you can also import it manually: -----BEGIN PGP PUBLIC KEY BLOCK----- mQENBF0RBLEBCADDYjb41eiWph7rY6d0R2Hp5e1ewiTH2Kn1Kg3CPMG2GS/0Kivu liTAkrHXcoAFB3h0OBJ+Q38Bh5Q0IYTh17eTVuYRj7olxD6D2jwynPJCXxUff0BS
From Drew DeVault to ~sircmpwn/sr.ht-dev
Thanks! To git.sr.ht:~sircmpwn/paste.sr.ht 6ac7dea..28e5b4c master -> master If you were interested in working more on this, a nice next step from table support would be parsing YAML frontmatter in markdown files and rendering a table for it like gist does.
From Drew DeVault to ~sircmpwn/sr.ht-dev
I applied your patch because it is indeed an unused import in this file, but you are correct that it won't make builds.sr.ht optional because scm.sr.ht still depends on it. However, I would accept another patch which indeed makes it optional by avoiding this code when there's no builds.sr.ht configuration set in the config.ini file. Thanks! To git.sr.ht:~sircmpwn/git.sr.ht 6dff624..96eecc0 master -> master
From Drew DeVault to ~sircmpwn/aerc
On Mon Jun 24, 2019 at 11:20 AM Frode Aannevik wrote: > did some, and I think it is a better approach to > use it instead of XOAUTH as it may be better supported > by other email providers > > the downside with it seems only to be its lib support [1] > > 1: https://github.com/emersion/go-sasl/issues/6 Gotcha. I would rather pursue it than merge XOAUTH support, even if it means we have to start by implementing it in go-sasl first.