From: Stefan Kangas <stefankangas@gmail.com>
To: Protesilaos Stavrou <info@protesilaos.com>, 43944@debbugs.gnu.org
Subject: bug#43944: 28.0.50; Update modus-operandi, modus-vivendi themes to v0.13.0
Date: Fri, 16 Oct 2020 10:13:58 -0700 [thread overview]
Message-ID: <CADwFkmmQ3m4ktMG7Wt=Gk1aH3bn0JCffNaLm7Vbe-2frNCFE8w@mail.gmail.com> (raw)
In-Reply-To: <874kn0ympd.fsf@protesilaos.com>
Protesilaos Stavrou <info@protesilaos.com> 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?
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.
> + 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.)
> + 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?
next prev parent reply other threads:[~2020-10-16 17:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 6:37 bug#43944: 28.0.50; Update modus-operandi, modus-vivendi themes to v0.13.0 Protesilaos Stavrou
2020-10-16 10:50 ` Stefan Kangas
2020-10-16 17:13 ` Stefan Kangas [this message]
2020-10-17 7:13 ` Protesilaos Stavrou
2020-10-17 16:23 ` Stefan Kangas
2020-10-19 8:12 ` Protesilaos Stavrou
2020-10-19 12:18 ` Stefan Kangas
2020-10-19 12:31 ` Protesilaos Stavrou
2020-10-19 12:57 ` Protesilaos Stavrou
2020-10-19 15:42 ` Stefan Kangas
[not found] <draft-87v9ffz1wx.fsf@stefankangas.se>
2020-10-16 13:46 ` Stefan Kangas
2020-10-16 15:30 ` Eli Zaretskii
2020-10-16 20:39 ` Protesilaos Stavrou
2020-10-17 0:07 ` Stefan Kangas
2020-10-17 7:15 ` Protesilaos Stavrou
2020-10-17 7:13 ` Eli Zaretskii
2020-10-17 8:09 ` Protesilaos Stavrou
2020-10-17 8:59 ` Basil L. Contovounesios
2020-10-19 8:08 ` Protesilaos Stavrou
2020-10-19 16:34 ` Basil L. Contovounesios
2020-10-19 16:55 ` Protesilaos Stavrou
2020-10-19 17:11 ` Basil L. Contovounesios
2020-10-19 16:59 ` Stefan Kangas
2020-10-19 17:12 ` Basil L. Contovounesios
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkmmQ3m4ktMG7Wt=Gk1aH3bn0JCffNaLm7Vbe-2frNCFE8w@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=43944@debbugs.gnu.org \
--cc=info@protesilaos.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).