From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: tomi.p.sarvela@intel.com, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [Intel-gfx] Random submitter change in Freedesktop Patchwork
Date: Thu, 20 Oct 2022 09:00:40 -0700 [thread overview]
Message-ID: <878rlaqyc7.wl-ashutosh.dixit@intel.com> (raw)
The freedesktop Patchwork seems to have a "feature" where in some cases the
submitter for a series changes randomly to a person who did not actually
submit a version of the series.
Not sure but this changed submitter seems to be a maintainer:
------------------------------------------------
https://patchwork.freedesktop.org/series/108156/
Original submission by badal.nilawar@intel.com and subsequent submissions
by me (ashutosh.dixit@intel.com) but current submitter is
jani.nikula@linux.intel.com.
For the above series I believe the submitter changed at v7 where perhaps a
rebuild or a retest was scheduled (not sure if Jani did it and that changed
something) but the build failed at v7. Also note root msg-id's for v6 and
v7 are the same.
------------------------------------------------
https://patchwork.freedesktop.org/series/108091/
Original submission by me (ashutosh.dixit@intel.com) but current submitter
is rodrigo.vivi@intel.com.
Similarly here submitter seems to have changed at v3 where again the build
failed. Also note root msg-id's for v2 and v3 are the same.
------------------------------------------------
The problem this change of submitter causes is that if the actual original
submitter wants to schedule a retest they cannot do it using the retest
button.
Thanks.
--
Ashutosh
WARNING: multiple messages have this Message-ID (diff)
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: tomi.p.sarvela@intel.com, Petri Latvala <petri.latvala@intel.com>,
Badal Nilawar <badal.nilawar@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Random submitter change in Freedesktop Patchwork
Date: Thu, 20 Oct 2022 09:00:40 -0700 [thread overview]
Message-ID: <878rlaqyc7.wl-ashutosh.dixit@intel.com> (raw)
The freedesktop Patchwork seems to have a "feature" where in some cases the
submitter for a series changes randomly to a person who did not actually
submit a version of the series.
Not sure but this changed submitter seems to be a maintainer:
------------------------------------------------
https://patchwork.freedesktop.org/series/108156/
Original submission by badal.nilawar@intel.com and subsequent submissions
by me (ashutosh.dixit@intel.com) but current submitter is
jani.nikula@linux.intel.com.
For the above series I believe the submitter changed at v7 where perhaps a
rebuild or a retest was scheduled (not sure if Jani did it and that changed
something) but the build failed at v7. Also note root msg-id's for v6 and
v7 are the same.
------------------------------------------------
https://patchwork.freedesktop.org/series/108091/
Original submission by me (ashutosh.dixit@intel.com) but current submitter
is rodrigo.vivi@intel.com.
Similarly here submitter seems to have changed at v3 where again the build
failed. Also note root msg-id's for v2 and v3 are the same.
------------------------------------------------
The problem this change of submitter causes is that if the actual original
submitter wants to schedule a retest they cannot do it using the retest
button.
Thanks.
--
Ashutosh
next reply other threads:[~2022-10-20 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 16:00 Dixit, Ashutosh [this message]
2022-10-20 16:00 ` Random submitter change in Freedesktop Patchwork Dixit, Ashutosh
2022-10-20 16:07 ` [Intel-gfx] " Jani Nikula
2022-10-20 16:07 ` Jani Nikula
2022-10-20 16:20 ` [Intel-gfx] " Ville Syrjälä
2022-10-20 16:20 ` Ville Syrjälä
2022-10-20 23:47 ` Lucas De Marchi
2022-10-20 23:47 ` Lucas De Marchi
2022-10-21 9:39 ` Saarinen, Jani
2022-10-21 9:39 ` Saarinen, Jani
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=878rlaqyc7.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=tomi.p.sarvela@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 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.