From: Tassilo Horn <tassilo@member.fsf.org>
To: ding@gnus.org
Subject: Re: thread sorting
Date: Wed, 04 May 2011 12:35:52 +0200 [thread overview]
Message-ID: <877ha6n46v.fsf@member.fsf.org> (raw)
In-Reply-To: <m2k4e6garh.fsf@randomsample.de> (David Engster's message of "Wed, 04 May 2011 09:55:46 +0200")
David Engster <deng@randomsample.de> writes:
Hi David,
>> Yeah, for tiny changes you don't have to sign papers. But Reiner
>> suggested that tiny changes have to be "marked" as such, and I have
>> no clue what marking means in this context.
>
> Just write "(tiny change)" in the ChangeLog. See
>
> http://www.gnu.org/prep/maintain/html_node/Legally-Significant.html
Thanks for the pointer. Done!
Bye,
Tassilo
--
Sent from my Emacs
prev parent reply other threads:[~2011-05-04 10:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 7:16 Peter Münster
2011-05-03 12:28 ` Tassilo Horn
2011-05-03 13:21 ` Peter Münster
2011-05-03 18:04 ` Tassilo Horn
2011-05-03 20:45 ` Reiner Steib
2011-05-04 6:32 ` Tassilo Horn
2011-05-04 7:05 ` Peter Münster
2011-05-04 7:15 ` Tassilo Horn
2011-05-04 7:55 ` David Engster
2011-05-04 10:35 ` Tassilo Horn [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=877ha6n46v.fsf@member.fsf.org \
--to=tassilo@member.fsf.org \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).