From: Gabriele Monaco <gmonaco@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Akhilesh Patil <akhilesh@ee.iitb.ac.in>,
Nam Cao <namcao@linutronix.de>,
Palmer Dabbelt <palmer@dabbelt.com>,
Zhen Ni <zhen.ni@easystack.cn>
Subject: Re: [GIT PULL] rv fixes for 6.17-rc7
Date: Tue, 16 Sep 2025 05:24:16 +0000 (UTC) [thread overview]
Message-ID: <a3563dcd-80e1-4091-87ae-f1ce1e22bf6e@redhat.com> (raw)
In-Reply-To: <20250915192527.38f80056@gandalf.local.home>
2025-09-15T23:24:35Z Steven Rostedt <rostedt@goodmis.org>:
> On Mon, 15 Sep 2025 09:35:30 +0200
> Gabriele Monaco <gmonaco@redhat.com> wrote:
>
>> Steve,
>>
>
> Hi Gabriele,
>
>> The following changes since commit 76eeb9b8de9880ca38696b2fb56ac45ac0a25c6c:
>>
>> Linux 6.17-rc5 (2025-09-07 14:22:57 -0700)
>>
>> are available in the Git repository at:
>>
>> git@gitlab.com:glemco/linux tags/rv-6.17-rc7
>
> Note, the above git path requires having a git account and permission to
> your repo. Is your repo public? I can't even see it on:
>
> https://github.com/glemco?tab=repositories
>
Hi Steve,
note the link above is gitLab:
https://gitlab.com/glemco/linux/-/tree/rv-6.17-rc7?ref_type=tags
and yes it's public.
But sure I'll switch to kernel.org as soon as I get an account.
> Also, it shouldn't be "tags/", just show the tag itself.
Mmh, I used the git request-pull [1] command and that's what it produces. I guess I'll go back to a hand crafted message, then.
Thanks,
Gabriele
[1] - https://git-scm.com/docs/git-request-pull
next prev parent reply other threads:[~2025-09-16 5:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 7:35 Gabriele Monaco
2025-09-15 23:25 ` Steven Rostedt
2025-09-16 5:24 ` Gabriele Monaco [this message]
2025-09-16 9:37 ` Gabriele Monaco
-- strict thread matches above, loose matches on Subject: below --
2025-09-17 8:42 Gabriele Monaco
2025-09-17 7:58 Gabriele Monaco
2025-09-15 7:31 Gabriele Monaco
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=a3563dcd-80e1-4091-87ae-f1ce1e22bf6e@redhat.com \
--to=gmonaco@redhat.com \
--cc=akhilesh@ee.iitb.ac.in \
--cc=linux-kernel@vger.kernel.org \
--cc=namcao@linutronix.de \
--cc=palmer@dabbelt.com \
--cc=rostedt@goodmis.org \
--cc=zhen.ni@easystack.cn \
/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
all inboxes | Powered by JetHome®