Hi folks,
I’ve had issues getting a reliable patch review/push workflow
going, and would like to hear what others are doing for this.
Specific issues I’d like to solve:
* `mumi am' sometimes claims not to find patches.
This just happened to me:
guix!env!ieure:~/projects/guix/staging$ mumi current 77009
77009 [PATCH] gnu: Add emacs-elfeed-tube. patch team-emacs
unanswered
opened 27 hours ago by Cayetano Santos
guix!env!ieure:~/projects/guix/staging$ mumi am -- -s
No patches found
I retried it a few minutes later, and it worked. I would like
something that works consistently /every/ time.
* guix-patches repo sometimes lags.
I have https://git.qa.guix.gnu.org/git/guix-patches as a remote on
my Guix clone. Sometimes I can `git cherry-pick -s issue-NNNN',
but other times, the patch hasn’t been processed yet.
* `debbugs-gnu-apply-patch' loses metadata
I like the idea of using debbugs to apply patches, since it
requires less tooling. However, while it reliably applies the
patch itself, it loses the commit message and committer
information. Is there some way to make it work more like `mumi
am'?
* Git hooks prevent pushing from with `guix shell'.
I apply patches & run builds in a `guix shell -m manifest.scm
openssh --pure'. However, .git/hooks/pre-push hardcodes `guix',
which isn’t available in this environment, meaning I have to
constantly jump in/out of the guix shell, or keep a second shell
open just to `git push'.
While I can push from Magit, it runs `make' during its validation,
and doesn’t run in the same environment. Depending on the patch,
this can fail, which means I have to switch to the `guix shell',
run `make', then push from Magit.
I would like to have a single session that can both build patches
and push commits.
If anyone has workflow bits I can use that improve on any of
these, I’d be grateful to hear about them.
Thanks,
-- Ian
