all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Cayetano Santos via Guix-patches via <guix-patches@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 68386@debbugs.gnu.org
Subject: [bug#68386] [PATCH v1] gnu: Add emacs-vhdl-mode.
Date: Wed, 17 Jan 2024 17:11:13 +0100	[thread overview]
Message-ID: <87v87s546m.fsf@inventati.org> (raw)
In-Reply-To: <87r0ignjc8.fsf@gmail.com>


>mer. 17 janv. 2024 at 09:08, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:

> Hi,
>
> Cayetano Santos <csantosb@inventati.org> writes:
>
>>>dim. 14 janv. 2024 at 21:46, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>>
>>> Since there already is a 'vhdl-mode' package shipped with Emacs, I think
>>> it's important to describe how this one differs (what improvements, features,
>>> refinements, etc. does it provide that would make it worth considering
>>> it instead of the default Emacs-provided option?).
>>
>> There are also many other packages (org, modus-themes, etc.) shipped with
>> Emacs that we package in its most recent versions (and many others that
>> pull these as propagated inputs, for some reason, even when already
>> available with Emacs). Do we also describe how they differ ?
>>
>> Anyway, the release notes, update history, bug fixes and enhancements of
>> every single version of vhdl-mode are given in the project home page,
>> already included along with the package. Where do we need to replicate
>> this information exactly for the patch to be accepted ?
>
> Oh, I hadn't noticed that this was the very same package that comes with
> Emacs.  I guess it's fine then, but to avoid any misunderstanding,
> perhaps the description text could mention it explicitly ("This is the
> same @code{vhdl-mode} that comes with Emacs, albeit it may be newer") or
> similar wording.

Done.

As an aside note, at some point, it should be decided how do we handle newest
releases of packages already included with emacs: do we need to mention
it explicitly or something else ?

C.




  reply	other threads:[~2024-01-17 16:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11 14:51 [bug#68386] [PATCH] gnu: Add emacs-vhdl-mode Cayetano Santos via Guix-patches via
2024-01-11 14:56 ` [bug#68386] [PATCH v1] " Cayetano Santos via Guix-patches via
2024-01-15  2:46   ` Maxim Cournoyer
2024-01-15  7:30     ` Cayetano Santos via Guix-patches via
2024-01-17 14:08       ` Maxim Cournoyer
2024-01-17 16:11         ` Cayetano Santos via Guix-patches via [this message]
2024-01-17 19:39           ` Maxim Cournoyer
2024-01-17 16:10 ` [bug#68386] [PATCH v2] " Cayetano Santos via Guix-patches via
2024-01-19  3:47   ` bug#68386: " Maxim Cournoyer
2024-01-19  7:28     ` [bug#68386] " Cayetano Santos via Guix-patches via
2024-01-19 21:58       ` Maxim Cournoyer

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=87v87s546m.fsf@inventati.org \
    --to=guix-patches@gnu.org \
    --cc=68386@debbugs.gnu.org \
    --cc=csantosb@inventati.org \
    --cc=maxim.cournoyer@gmail.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.