On 2020-10-16, 10:13 -0700, Stefan Kangas wrote: > Protesilaos Stavrou writes: > >> + The two themes are also available in GNU ELPA. What is the best way >> to ensure that we sync between emacs.git and elpa.git? GNU ELPA has >> hitherto pulled from dedicated branches on my upstream git repository. >> Maybe it would be better/easier to start building directly from the >> Emacs source? This would reduce the overall workload. > > What does "start building directly from the Emacs source" mean here? "Build" is the wrong term here. Sorry about that! My intent is to find an easy way/workflow to get the files from Emacs into GNU ELPA. And by "easy" I mean not to duplicate the work we do here. So I would not have to contact the GNU ELPA maintainers separately and have them pull from my git source. > FWIW, I don't think we should feel too bound to any particular process; > this seems like a practical matter where we should try to do whatever > is most practical. Good to know. I have no particular preference on the matter and shall adapt to whatever you and others may recommend. >> + Sending attachments with large diffs has the downside of losing the >> commit history. Do Emacs maintainers wish to keep track of it? If >> so, what would be the best way to preserve it, seeing as I am >> developing them on my own upstream? > > I don't think we generally worry about preserving history for packages > managed externally. We just sync the latest version. > > (If one really would like to preserve it, it could perhaps be done with > some git magic. I'm not sure it's worth the extra effort.) Syncing the latest version works fine for me. I have thus far published tagged releases on a monthly cadence. Expect the next one in mid to late November. >> + Should the texinfo file be mentioned in the NEWS entry about the two >> themes? The attached patch does not include such a change. > > We could of course add a NEWS entry for it. Would you like to propose > one? I attach a possible rewording that also corrects "colour" and adds an explicit reference to the WCAG AAA accessibility spec. Please note that I do not know how to properly reference an Info node: I used 'C-u 0 x', which calls 'Info-copy-current-node-name'. -- Protesilaos Stavrou protesilaos.com