From: Antonio Argenziano <antonio.argenziano@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>, igt-dev@lists.freedesktop.org
Cc: Petri Latvala <petri.latvala@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] doc: End transition period.
Date: Tue, 5 Feb 2019 14:52:48 -0800 [thread overview]
Message-ID: <e35ce776-1ae3-bc6d-ae15-c09984a899c9@intel.com> (raw)
In-Reply-To: <20190205221805.32361-1-rodrigo.vivi@intel.com>
On 05/02/19 14:18, Rodrigo Vivi wrote:
> igt-dev is pretty established after a 1-year transition.
>
> Let's end the transition and avoid confusion.
>
> Cc: Easwar Hariharan <easwar.hariharan@intel.com>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Petri Latvala <petri.latvala@intel.com>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> CONTRIBUTING.md | 18 ------------------
> autogen.sh | 3 ---
> meson.sh | 2 --
> 3 files changed, 23 deletions(-)
>
> diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
> index 27c8e796..c2169375 100644
> --- a/CONTRIBUTING.md
> +++ b/CONTRIBUTING.md
> @@ -10,24 +10,6 @@ A short list of contribution guidelines:
>
> Development mailing list for IGT GPU Tools <igt-dev@lists.freedesktop.org>
>
> - For a transition period patches are accepted on both the igt-dev mailing list
> - and the former intel-gfx mailing list (with the appropriate patch
> - subjectprefix, see below).
> -
> - During the transition period, feel free to send patches to both lists if you
> - have a need to do so, as they will get deduplicated so they only appear and
> - are tested in one Patchwork instance.
> -
> - Intel GFX discussion <intel-gfx@lists.freedesktop.org>
> -
> - Please use --subject-prefix="PATCH i-g-t" so IGT patches are easily
> - identified in the massive amount mails on intel-gfx. To ensure this is always
> - done, meson.sh (and autogen.sh) will run:
> -
> - git config format.subjectprefix "PATCH i-g-t"
IIRC, the agreement was that patches will still be sent to intel-gfx if
they affect the driver. So, keeping the prefix would still be useful.
Antonio
> -
> - on its first invocation.
> -
> - igt-gpu-tools is MIT licensed and we require contributions to follow the
> developer's certificate of origin: http://developercertificate.org/
>
> diff --git a/autogen.sh b/autogen.sh
> index 65fcab2f..55764070 100755
> --- a/autogen.sh
> +++ b/autogen.sh
> @@ -9,9 +9,6 @@ cd $srcdir
> autoreconf -v --install || exit 1
> cd $ORIGDIR || exit $?
>
> -git config --local --get format.subjectPrefix >/dev/null 2>&1 ||
> - git config --local format.subjectPrefix "PATCH i-g-t"
> -
> if test -z "$NOCONFIGURE"; then
> $srcdir/configure "$@"
> fi
> diff --git a/meson.sh b/meson.sh
> index 7cf9d4a3..3d5d8e9a 100755
> --- a/meson.sh
> +++ b/meson.sh
> @@ -35,6 +35,4 @@ docs:
>
> EOF
>
> -git config format.subjectprefix "PATCH i-g-t"
> -
> make $@
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-02-05 22:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 22:18 [igt-dev] [PATCH i-g-t] doc: End transition period Rodrigo Vivi
2019-02-05 22:52 ` Antonio Argenziano [this message]
2019-02-11 19:18 ` Rodrigo Vivi
2019-02-15 10:44 ` Petri Latvala via igt-dev
2019-02-15 17:45 ` Rodrigo Vivi via igt-dev
2019-02-15 18:57 ` Rodrigo Vivi via igt-dev
2019-02-15 19:02 ` Hariharan, Easwar via igt-dev
2019-02-19 17:53 ` Rodrigo Vivi
2019-02-05 22:53 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-02-06 4:15 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-02-15 18:15 ` [igt-dev] ✓ Fi.CI.BAT: success for doc: End transition period. (rev2) Patchwork
2019-02-15 19:35 ` [igt-dev] ✓ Fi.CI.BAT: success for doc: End transition period. (rev3) Patchwork
2019-02-15 21:27 ` [igt-dev] ✗ Fi.CI.IGT: failure for doc: End transition period. (rev2) Patchwork
2019-02-16 0:07 ` [igt-dev] ✓ Fi.CI.IGT: success for doc: End transition period. (rev3) Patchwork
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=e35ce776-1ae3-bc6d-ae15-c09984a899c9@intel.com \
--to=antonio.argenziano@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=petri.latvala@intel.com \
--cc=rodrigo.vivi@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox