list mirror (unofficial, one of many)
 help / color / mirror / Atom feed
From: Junio C Hamano <>
Subject: Re: [PATCH] CoC: update to version 2.0 + local changes
Date: Wed, 13 Jan 2021 01:05:09 -0800
Message-ID: <> (raw)
In-Reply-To: <> (Junio C. Hamano's message of "Wed, 13 Jan 2021 00:33:23 -0800")

Junio C Hamano <> writes:

> Here is to remind those of you who may want to add your Acked-by to
> Ævar's proposed update to show your support.  I've collected ones on
> the list I saw in replies to the original proposal [*1*] but in case
> I missed yours...
> Thanks.
> ...
> [Reference]
> *1* Message-Id: <>
> ----- >8 ---------- >8 ---------- >8 ---------- >8 ---------- >8 -----
> From: Ævar Arnfjörð Bjarmason <>
> Subject: [PATCH] CoC: update to version 2.0 + local changes
> Update the CoC added in 5cdf2301 (add a Code of Conduct document,
> 2019-09-24 from version 1.4 to version 2.0. This is the version found
> at [1] with the following minor changes:
>  - We preserve the change to the CoC in 3f9ef874a73 (CODE_OF_CONDUCT:
>    mention individual project-leader emails, 2019-09-26)
>  - We preserve the custom intro added in 5cdf2301d4a (add a Code of
>    Conduct document, 2019-09-24)
> This change intentionally preserves a warning emitted on "git diff
> --check". It's better to make it easily diff-able with upstream than
> to fix whitespace changes in our version while we're at it.
> 1.
> Signed-off-by: Ævar Arnfjörð Bjarmason <>
> Acked-by: Christian Couder <>
> Acked-by: Derrick Stolee <>
> Acked-by: Elijah Newren <>
> Acked-by: Johannes Schindelin <>
> Acked-by: Jonathan Nieder <>
> Acked-by: brian m. carlson <>
> Signed-off-by: Junio C Hamano <>
> ---

I guess I should lead by an example ;-)  The above misses mine and
Signed-off-by means a totally different thing [*1*] from Acked-by.

    Acked-by: Junio C Hamano <>


*1* Most importantly, signing off is about recording provenance of
    the change. You certify that you have enough rights to pass the
    patch along to the project, and you agree that the fact that you
    contributed the patch will be recorded in perpetuity.  It does
    not mean that you agree to the change in the patch and you do
    not assure correctness of the patch by signing it off.  I signed
    off the above patch to say I got it from Ævar and committing it
    as-is, but it does not say that I agree with the move of our CoC
    to Contributor Covenant 2.0, hence my Ack here.

  reply	other threads:[~2021-01-13  9:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-13  8:33 Junio C Hamano
2021-01-13  9:05 ` Junio C Hamano [this message]
2021-01-13 17:55   ` Jeff King
2021-01-13 15:25 ` Taylor Blau
2021-01-13 18:58 ` Jonathan Tan

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link list mirror (unofficial, one of many)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 git git/ \
	public-inbox-index git

Example config snippet for mirrors.
Newsgroups are available over NNTP:
 note: .onion URLs require Tor:

code repositories for the project(s) associated with this inbox:

AGPL code for this site: git clone