From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
"Schulman, Andrew" <schulman.andrew@epa.gov>
Subject: Re: [ITP] fish-doc
Date: Mon, 3 Apr 2023 18:01:53 +0100 [thread overview]
Message-ID: <618f313b-7285-b93f-20fe-b2bc171e4309@dronecode.org.uk> (raw)
In-Reply-To: <r5rl2i1fu07adc672hkus7i85nkjregmvf@4ax.com>
On 03/04/2023 16:16, Andrew Schulman via Cygwin-apps wrote:
> In the next release of fish, I'm going to split the package into fish and
> fish-doc. I can't remember if someone needs to add me to the maintainers list
> for the new fish-doc package, or if that happens automatically since they're
> created from the same source package.
>
> If someone does need to add me as the maintainer of fish-doc, can you please do
> that?
No action is necessary, please go ahead.
(Things get more complex if the install package name is already claimed
by another source package, but that seems unlikely to be the case here.)
prev parent reply other threads:[~2023-04-03 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 15:16 Andrew Schulman
2023-04-03 17:01 ` Jon Turney [this message]
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=618f313b-7285-b93f-20fe-b2bc171e4309@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=schulman.andrew@epa.gov \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).