From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Yang, Dong" <dong.yang@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: patc push failed
Date: Mon, 05 Aug 2019 13:09:41 +0300 [thread overview]
Message-ID: <87tvavkjoa.fsf@intel.com> (raw)
In-Reply-To: <CFEFE6A4B6B19549BBA2CEC86E99FAA03619D71C@SHSMSX104.ccr.corp.intel.com>
On Mon, 05 Aug 2019, "Yang, Dong" <dong.yang@intel.com> wrote:
> I have clone the drm-intel code-base, after I apply my patch locally
> and I want upstream the patch, but it report error: fatal: unable to
> access 'https://anongit.freedesktop.org/git/drm-intel.git/': The
> requested URL returned error: 403
>
> I use git clone to clone the code-base:
> git clone https://anongit.freedesktop.org/git/drm-intel.git
>
> and git push to upstream the patch.
>
> Anybody can help to tell me what wrong?
You need to submit your patches by email for review on the intel-gfx
mailing list. See git format-patch and/or git send-email. There's a
plethora of information available at [1].
Only drm-intel maintainers and committers have access to push the
reviewed and tested patches to the upstream git repository.
BR,
Jani.
[1] https://www.kernel.org/doc/html/latest/process/index.html
(also Documentation/process/ in the kernel source tree)
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2019-08-05 10:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 6:03 patc push failed Yang, Dong
2019-08-05 10:09 ` Jani Nikula [this message]
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=87tvavkjoa.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dong.yang@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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.