unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: oub@mat.ucm.es, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: copyright issues and derivative work (the case of matlab-mode)
Date: Thu, 25 Nov 2021 10:33:32 +0200	[thread overview]
Message-ID: <83ee747hyb.fsf@gnu.org> (raw)
In-Reply-To: <87lf1czm6g.fsf@yahoo.com> (message from Po Lu on Thu, 25 Nov 2021 16:14:47 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: rms@gnu.org,  oub@mat.ucm.es,  emacs-devel@gnu.org
> Date: Thu, 25 Nov 2021 16:14:47 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> Perhaps we should send a message about this point
> >> to each person with commit access.  Our committers would more
> >> reliably do it, with this reminder.
> 
> FWIW, I have heard that `git am' will do this automatically.

Only if the patch was formatted with "git format-patch".  Which is why
we prefer that, see below.

> Perhaps it would be a good idea to suggest people to always use `git am'
> to install changes made by others?

This is trivial for anyone who installs patches, and I very much doubt
that anyone doesn't use that already.  CONTRIBUTE hints on that:

  However, we prefer the 'git format-patch' method with attachment, as
  doing so delivers patches in the correct and easily-recognizable format
  more reliably, and makes the job of applying the patches easier and less
  error-prone.  It also allows sending patches whose author is someone
  other than the email sender.

Note the last sentence.  It doesn't mention "git am" because it is a
trivium, but it's clear it assumes that.

I don't think we should have a Git tutorial as part of Emacs; someone
who gets write access to the repository is supposed to be sufficiently
proficient in Git commands.  We don't explain too much about how to
push, either, for the same reason.

Let's not make a mountain out of a molehill.



  reply	other threads:[~2021-11-25  8:33 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23 16:25 copyright issues and derivative work (the case of matlab-mode) Uwe Brauer
2021-11-23 16:44 ` Eli Zaretskii
2021-11-23 16:59   ` Uwe Brauer
2021-11-23 17:18     ` Eli Zaretskii
2021-11-23 17:45       ` Uwe Brauer
2021-11-23 18:17         ` Eli Zaretskii
2021-11-25  5:31           ` Richard Stallman
2021-11-25  7:59             ` Eli Zaretskii
2021-11-25  8:03               ` Uwe Brauer
2021-11-25  8:05                 ` Eli Zaretskii
2021-11-27  4:08                   ` Richard Stallman
2021-11-27  6:19                     ` Eli Zaretskii
2021-11-28  4:24                       ` Richard Stallman
2021-11-28  8:09                         ` Eli Zaretskii
2021-11-29  3:02                           ` Richard Stallman
2021-11-29  3:32                             ` Eli Zaretskii
2021-11-30  4:10                               ` Richard Stallman
2021-11-30 16:45                                 ` Eli Zaretskii
2021-12-01  7:05                                   ` Richard Stallman
2021-11-25  8:14               ` Po Lu
2021-11-25  8:33                 ` Eli Zaretskii [this message]
2021-11-25  9:19                   ` Uwe Brauer
2021-11-23 19:56         ` Stefan Monnier
2021-11-24  8:06           ` Uwe Brauer
2021-11-23 20:00         ` Stefan Monnier
2021-11-24  8:00           ` Uwe Brauer
2021-11-24 13:30             ` Stefan Monnier
2021-11-24  4:28         ` Richard Stallman
2021-11-24  7:42           ` Uwe Brauer
2021-11-27  3:24             ` Eric Ludlam
2021-11-28  4:20               ` Richard Stallman
2021-11-28  9:16               ` Uwe Brauer
2021-11-23 20:00     ` Tassilo Horn
2021-11-24  4:31   ` Richard Stallman
2021-11-24  7:40     ` Uwe Brauer

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=83ee747hyb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=oub@mat.ucm.es \
    --cc=rms@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).