From: Wim Van Sebroeck <wim@linux-watchdog.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Watchdog Mailing List <linux-watchdog@vger.kernel.org>,
Guenter Roeck <linux@roeck-us.net>, Arnd Bergmann <arnd@arndb.de>,
Jeff Johnson <quic_jjohnson@quicinc.com>
Subject: Re: [GIT PULL REQUEST] watchdog - v6.10 release cycle (fixes).
Date: Sun, 30 Jun 2024 11:14:03 +0200 [thread overview]
Message-ID: <20240630091403.GA12993@www.linux-watchdog.org> (raw)
In-Reply-To: <CAHk-=whgnEuO1+8Gk3AiWeuSeAuCoUWnkuxUvczHwfJL+juAsA@mail.gmail.com>
Hi Linus,
> On Tue, 25 Jun 2024 at 06:51, Wim Van Sebroeck <wim@linux-watchdog.org> wrote:
> >
> > git://www.linux-watchdog.org/linux-watchdog.git linux-watchdog-6.10-rc-fixes
>
> ENOSUCHTAG.
>
> I do see the commit you mention in HEAD, but there's no actual signed
> tag referencing it.
>
> Forgot to push out (and then didn't react to the error messages that
> git request-pull gave you)?
It didn't gave me any warnings, so I took time to investigate it this morning.
Turns out I did not do it on the linux-watchdog tree but on the linux-watchog-next tree :-( .
Such a stupid mistake from my side...
I'll fix it and will come back.
Kind regards,
Wim.
next prev parent reply other threads:[~2024-06-30 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 13:31 [GIT PULL REQUEST] watchdog - v6.10 release cycle (fixes) Wim Van Sebroeck
2024-06-26 15:50 ` Linus Torvalds
2024-06-30 9:14 ` Wim Van Sebroeck [this message]
2024-06-30 9:44 ` Wim Van Sebroeck
2024-06-30 15:46 ` pr-tracker-bot
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=20240630091403.GA12993@www.linux-watchdog.org \
--to=wim@linux-watchdog.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=quic_jjohnson@quicinc.com \
--cc=torvalds@linux-foundation.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.