unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Dov Grobgeld <dov.grobgeld@gmail.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: [PATCH] color-hsv-to-rgb
Date: Mon, 16 Oct 2023 07:59:49 +0000	[thread overview]
Message-ID: <CADwFkm=zvW65qY90uRwU8w0nJENc2E1Rk4HFoX0-efQ-nFFMzA@mail.gmail.com> (raw)
In-Reply-To: <CA++fsGEWeYerMqb1Mgd0bW7rQRvhqkeK_g296D8rNpTMv2fzTw@mail.gmail.com>

Dov Grobgeld <dov.grobgeld@gmail.com> writes:

> I would like to do my first(!) contribution to emacs with the attached
> patch. Is there interest, or is it too trivial? Do I need to do a copyright
> assignment? Is there a guide for dummies on how to do that?

Welcome to Emacs!

I don't see why we couldn't take a patch implementing the inverse of
`color-rgb-to-hsv', so I think there's interest.  It would be
interesting to know what you need it for, though.

Your patch is above 15 lines, so we would need a copyright assignment
for it.  See the form below.  When the assignment is done, please send
your patch to bug-gnu-emacs@gnu.org, which will record it in our bug
tracker.  We risk losing track of patches sent to emacs-devel.

Thanks again for your interest in Emacs.

---

Please email the following information to assign@gnu.org, and we
will send you the assignment form for your past and future changes.

Please use your full legal name (in ASCII characters) as the subject
line of the message.
----------------------------------------------------------------------
REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES

[What is the name of the program or package you're contributing to?]
Emacs

[Did you copy any files or text written by someone else in these changes?
Even if that material is free software, we need to know about it.]

[Do you have an employer who might have a basis to claim to own
your changes?  Do you attend a school which might make such a claim?]

[For the copyright registration, what country are you a citizen of?]

[What year were you born?]

[Please write your email address here.]

[Please write your postal address here.]

[Which files have you changed so far, and which new files have you written
so far?]



  reply	other threads:[~2023-10-16  7:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-16  7:28 [PATCH] color-hsv-to-rgb Dov Grobgeld
2023-10-16  7:59 ` Stefan Kangas [this message]
2023-10-19 19:58   ` Jim Porter
2023-10-19 20:12     ` [External] : " Drew Adams
2023-10-19 21:22       ` Stefan Kangas
2023-10-19 21:35         ` Drew Adams
2023-10-20  6:09           ` Eli Zaretskii
2023-10-20 15:04             ` Drew Adams
2023-10-20 17:59               ` Eli Zaretskii
2023-10-16 12:05 ` Eli Zaretskii
2023-10-17  6:12   ` Dov Grobgeld

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='CADwFkm=zvW65qY90uRwU8w0nJENc2E1Rk4HFoX0-efQ-nFFMzA@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=dov.grobgeld@gmail.com \
    --cc=emacs-devel@gnu.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.
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).