all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Wolfgang Scherer <Wolfgang.Scherer@gmx.de>
Cc: 37185@debbugs.gnu.org
Subject: bug#37185: *** GMX Spamverdacht *** Re: bug#37185: 24.5.1: vc--add-line, vc--remove-regexp are sub-optimal
Date: Tue, 27 Aug 2019 10:37:01 +0300	[thread overview]
Message-ID: <83sgpndppe.fsf@gnu.org> (raw)
In-Reply-To: <12aa168d-54d2-93d9-ab7b-f35a5acaea13@gmx.de> (message from Wolfgang Scherer on Tue, 27 Aug 2019 00:52:47 +0200)

> Cc: 37185@debbugs.gnu.org
> From: Wolfgang Scherer <Wolfgang.Scherer@gmx.de>
> Date: Tue, 27 Aug 2019 00:52:47 +0200
> 
> > It is best to generate your patches using "git format-patch" and then
> > send them as an attachment, I think this will solve these problems,
> OK. I gave it a shot. Patch is attached.

Thanks, it looks good, but please wait for our VC expert to review it.

> Copyright-paperwork-exempt: yes

I don't think you need this, since your copyright assignment from 2002
is still on file.  If it became invalid since then, I suggest to start
your renewal legal paperwork now, as your contributions are already
beyond the limit we can accept without an assignment.  But if it is
still valid, then just don't use the Copyright-paperwork-exempt
header in the future.





  reply	other threads:[~2019-08-27  7:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-25 20:32 bug#37185: 24.5.1: vc--add-line, vc--remove-regexp are sub-optimal Wolfgang Scherer
2019-08-26  6:44 ` Eli Zaretskii
2019-08-26 22:52   ` bug#37185: *** GMX Spamverdacht *** " Wolfgang Scherer
2019-08-27  7:37     ` Eli Zaretskii [this message]
2019-08-27 23:38       ` bug#37185: *** GMX Spamverdacht *** " Wolfgang Scherer
2019-09-14  0:45       ` bug#37185: " Dmitry Gutov
2019-09-16 17:14         ` Wolfgang Scherer
2019-09-16 17:15         ` Wolfgang Scherer
2019-12-24 22:39           ` Dmitry Gutov

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=83sgpndppe.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=37185@debbugs.gnu.org \
    --cc=Wolfgang.Scherer@gmx.de \
    /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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.