From: Arun Isaac <arunisaac@systemreboot.net>
To: Diego Nicola Barbato <dnbarbato@posteo.de>
Cc: 35661@debbugs.gnu.org
Subject: [bug#35661] [PATCH] doc: Fix typo.
Date: Sun, 12 May 2019 03:50:56 +0530 [thread overview]
Message-ID: <cu7bm08ab07.fsf@systemreboot.net> (raw)
In-Reply-To: <87a7ft0zc4.fsf@GlaDOS.home>
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
> I was not aware that removing a single character would warrant the
> addition of a copyright header.
I am not aware of any policy about this in the Guix project. But, I have
seen people do it both ways -- both adding and not adding copyright
headers for trivial changes. So, I generally add copyright headers for
all changes no matter how trivial.
> I have made less trivial changes in the past and I have never added a
> copyright line. Should I do something about that?
I think you can ignore those instances. Even I have made trivial changes
before and not added a copyright header.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2019-05-11 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 21:19 [bug#35661] [PATCH] doc: Fix typo Diego Nicola Barbato
2019-05-11 7:44 ` bug#35661: " Arun Isaac
2019-05-11 15:45 ` [bug#35661] " Diego Nicola Barbato
2019-05-11 22:20 ` Arun Isaac [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cu7bm08ab07.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=35661@debbugs.gnu.org \
--cc=dnbarbato@posteo.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 public inbox
https://git.savannah.gnu.org/cgit/guix.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).