From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Contributors?
Date: Fri, 14 Mar 2014 10:49:46 -0400 [thread overview]
Message-ID: <5323170A.5020608@tresys.com> (raw)
In-Reply-To: <CAPhFHN_RPJ6evjcRQS1_M+hGsBAtYyXtwTyt7YMpq6eFUyEmGw@mail.gmail.com>
On 03/14/2014 10:29 AM, Shintaro Fujiwara wrote:
> I thought my patch was merged but my name was not in the Changelog in the latest version.
>
> Mine was too minor to be open to public?
>
> Thanks.
We're definitely not trying to avoid giving people credit for their contributions. I generate the changelog by using 'git shortlog'. If a patch is correctly sent via git format-patch and git send-email, I can apply it with git am, and the author will show up as you'd expect in the changelog (Like Dominick, Dan Walsh, and I do). Showing up as the author in the changelog is another reason to submit patches this way.
If Dominick or I have to manually apply a patch, we will show up as the author. We try to make sure the original author is mentioned in the commit message, but if we mistakenly forgot you, I apologize.
One thing you may be unaware of is that contrib now has its own changelog. I will create a symlink in the policy root directory to the contrib changelog. In the contrib changelog, I see that Dominick merged a patch from you that fixed a typo in ksmtuned_admin(); is this the patch you are referring to?
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2014-03-14 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 14:29 [refpolicy] Contributors? Shintaro Fujiwara
2014-03-14 14:49 ` Christopher J. PeBenito [this message]
2014-03-14 14:55 ` Dominick Grift
2014-03-14 15:06 ` Shintaro Fujiwara
2014-03-14 15:15 ` Shintaro Fujiwara
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=5323170A.5020608@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.tresys.com \
/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 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.