git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@freescale.com>
To: sverre@rabbelier.nl
Cc: "Abhijit Menon-Sen" <ams@toroid.org>,
	"Peter Valdemar Mørch" <4ux6as402@sneakemail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] Avoid warning when From: is encoded
Date: Fri, 25 Jul 2008 11:39:20 -0500	[thread overview]
Message-ID: <488A01B8.2010405@freescale.com> (raw)
In-Reply-To: <bd6139dc0807250901n7408a8e6w5dead238e897fc03@mail.gmail.com>

Sverre Rabbelier wrote:

> Acked-by is reserved for people who are "owners" of the area the patch
> touches.

I love pronouncements like this.  While that may be exactly true
for the Git project, it is not, in general, always true.  Within
parts of the Kernel development process, anyone who wants to may
ACK a patch if they have done some level of work to confirm that
it "is good", for some measure of "good", even if that is just
applying the patch and testing it.  It is re-assurance that other
people consider the patch acceptable.

Of course, if there are, say, multiple functional areas with
different maintainers, and the patch should go in via one repository
but crosses into a second or third functional area, getting the
ACK from the other maintainers may be considered essential for
its ultimate acceptance.  In that regard, yes, the maintainer's
ACK carries more weight.

> So for example, a patch to git-gui could be Acked-by Shawn O.
> Pierce, or one related to pack format by Nico (I think?). So you
> should Ack it if you have done (a lot of) work in the same area as the
> patch before and if the patch looks good.

Agreed.

jdl

  reply	other threads:[~2008-07-25 16:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25 13:06 [PATCH] Avoid warning when From: is encoded Peter Valdemar Mørch
2008-07-25 13:16 ` Abhijit Menon-Sen
2008-07-25 16:01   ` Sverre Rabbelier
2008-07-25 16:39     ` Jon Loeliger [this message]
2008-07-26  2:53       ` Johannes Schindelin
2008-07-25 16:33 ` Junio C Hamano
2008-07-25 18:38   ` Jeff King

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=488A01B8.2010405@freescale.com \
    --to=jdl@freescale.com \
    --cc=4ux6as402@sneakemail.com \
    --cc=ams@toroid.org \
    --cc=git@vger.kernel.org \
    --cc=sverre@rabbelier.nl \
    /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).