From: Boris Brezillon <boris.brezillon@collabora.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-i3c <linux-i3c@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] i3c: Changes for 5.8
Date: Mon, 1 Jun 2020 20:52:03 +0200 [thread overview]
Message-ID: <20200601205203.7677efc1@collabora.com> (raw)
In-Reply-To: <CAHk-=whW82ewxKJjaFq=96eEpCMN0=DtaZxX9ZGBH7BTgTkEfQ@mail.gmail.com>
Hello Linus,
On Mon, 1 Jun 2020 11:39:05 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Mon, Jun 1, 2020 at 12:54 AM Boris Brezillon
> <boris.brezillon@collabora.com> wrote:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/i3c/linux.git i3c/for-5.8
>
> Hmm. No such ref..
>
> I see the "i3c/next" branch that has that top commit, but I don't see
> the signed tag.
Oops, should be here now.
>
> Forgot to push?
I pushed it, but maybe not to the right repo.
> "git request-pull" _should_ have warned about the
> remote side missing..
Yes, it warned me about that but there used to be a slight delay
between the time I push at tag to the repo and the time it actually
appears there in the past (maybe it's no longer the case), so I didn't
pay attention to that one. I'll try to be more careful next time. Sorry
for the inconvenience.
Regards,
Boris
_______________________________________________
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
WARNING: multiple messages have this Message-ID (diff)
From: Boris Brezillon <boris.brezillon@collabora.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-i3c <linux-i3c@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] i3c: Changes for 5.8
Date: Mon, 1 Jun 2020 20:52:03 +0200 [thread overview]
Message-ID: <20200601205203.7677efc1@collabora.com> (raw)
In-Reply-To: <CAHk-=whW82ewxKJjaFq=96eEpCMN0=DtaZxX9ZGBH7BTgTkEfQ@mail.gmail.com>
Hello Linus,
On Mon, 1 Jun 2020 11:39:05 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Mon, Jun 1, 2020 at 12:54 AM Boris Brezillon
> <boris.brezillon@collabora.com> wrote:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/i3c/linux.git i3c/for-5.8
>
> Hmm. No such ref..
>
> I see the "i3c/next" branch that has that top commit, but I don't see
> the signed tag.
Oops, should be here now.
>
> Forgot to push?
I pushed it, but maybe not to the right repo.
> "git request-pull" _should_ have warned about the
> remote side missing..
Yes, it warned me about that but there used to be a slight delay
between the time I push at tag to the repo and the time it actually
appears there in the past (maybe it's no longer the case), so I didn't
pay attention to that one. I'll try to be more careful next time. Sorry
for the inconvenience.
Regards,
Boris
next prev parent reply other threads:[~2020-06-01 18:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 7:54 [GIT PULL] i3c: Changes for 5.8 Boris Brezillon
2020-06-01 7:54 ` Boris Brezillon
2020-06-01 18:39 ` Linus Torvalds
2020-06-01 18:39 ` Linus Torvalds
2020-06-01 18:52 ` Boris Brezillon [this message]
2020-06-01 18:52 ` Boris Brezillon
2020-06-01 19:35 ` pr-tracker-bot
2020-06-01 19:35 ` 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=20200601205203.7677efc1@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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.