From: unobe@cpan.org
To: 9front@9front.org
Subject: Patch-keeping (Was Re: [9front] PATCH: click-to-focus in fgui)
Date: Sat, 14 Aug 2021 13:57:03 -0700 [thread overview]
Message-ID: <C2AD5D063B3A78E96327C4C5A7AE8B37@smtp.pobox.com> (raw)
In-Reply-To: <CAA85C87T8hbUaL8=UC_bBKhgHjke+q57F54dz5cOBHpApbcPXg@mail.gmail.com>
Quoth José Miguel Sánchez García <soy.jmi2k@gmail.com>:
> Wanting focus-follows-mouse is reasonable. Wanting in-tree support for
> that in 9, not so much. #ifdefs are pointless, as they are a kind of
> sloppy, inline patch that makes the code harder to understand. I think
> patching is the way to go. And I'm personally one of those who keep a
> collection of patches I apply automatically after each 9front
> installation because I love customizing my system (currently I'm
> changing colors, menus, keybinds...).
Just curious about your patch-keeping procedure: by keeping around a
collection of patches, do you just have a separate branch that you
merge master changes to, or is it really a collection of patches
outside of a repo?
next prev parent reply other threads:[~2021-08-14 21:06 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 22:59 [9front] PATCH: click-to-focus in fgui Silas McCroskey
2021-08-10 14:19 ` ori
2021-08-11 5:28 ` rgl
2021-08-11 20:49 ` Philip Silva
2021-08-11 21:09 ` Steve Simon
2021-08-11 22:37 ` Xiao-Yong Jin
2021-08-12 9:05 ` hiro
2021-08-12 14:36 ` Eckard Brauer
2021-08-13 6:44 ` unobe
2021-08-13 7:10 ` hiro
2021-08-14 10:20 ` Eckard Brauer
2021-08-14 13:09 ` qwx
2021-08-14 15:03 ` Stuart Morrow
2021-08-14 13:17 ` José Miguel Sánchez García
2021-08-14 20:57 ` unobe [this message]
2021-08-14 15:04 ` Stuart Morrow
2021-08-14 18:08 ` hiro
2021-08-14 21:43 ` unobe
2021-08-15 6:47 ` hiro
2021-08-14 21:46 ` unobe
2021-08-15 13:36 ` Eckard Brauer
2021-08-15 19:16 ` hiro
2021-08-15 17:31 ` kvik
2021-08-15 18:34 ` Kurt H Maier
2021-08-15 18:48 ` Stanley Lieber
2021-08-15 20:18 ` Eckard Brauer
2021-08-15 22:35 ` Stanley Lieber
2021-08-16 5:14 ` Stanley Lieber
2021-08-16 15:46 ` Skylar Bleed
2021-08-15 19:03 ` hiro
2021-08-16 16:40 ` kvik
2021-08-16 19:25 ` Stuart Morrow
2021-08-16 19:40 ` Kurt H Maier
2021-08-17 2:05 ` Stanley Lieber
2021-08-16 20:04 ` hiro
2021-08-16 20:13 ` hiro
2021-08-17 1:10 ` Xiao-Yong Jin
2021-08-17 8:11 ` hiro
2021-08-12 0:12 ` hiro
2021-08-15 4:29 ` ori
2021-08-16 19:40 ` ori
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=C2AD5D063B3A78E96327C4C5A7AE8B37@smtp.pobox.com \
--to=unobe@cpan.org \
--cc=9front@9front.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 NNTP newsgroup(s).