July 18, 2023 at 1:14 AM, "Luben Tuikov" wrote:
> > > Not sure about other drivers--they can speak for themselves and the CC
> > > list
> > > should include them--please use "dim add-missing-cc" and make sure
> > > that the Git commit description contains the Cc tags--then git send-email
> > >
April 21, 2023 1:01 PM, "Krzysztof Kozlowski"
wrote:
>> Ah, got it. So I guess from the perspective of "b4" every time the
>> author modifies a patch (like adding new tags to it) then it's a new
>> application of Signed-off-by and thus the old Signed-off-by is removed
>> from the top and a new
On Fri, Mar 17, 2023 at 07:41:04PM +0100, Matthieu Baerts wrote:
> @Konstantin: would it be OK for your future Bugzilla bot to deal with
> the generic "Link:" tag instead of the specific "Closes:" one?
Yes and no -- we can easily figure out that "it's a bugzilla link and it
points at this bug",
On Thu, Mar 16, 2023 at 10:22:18AM +0100, Thorsten Leemhuis wrote:
> I liked Andrew's `have been using "Addresses:" on occasion. [...] more
> humble [...]` comment. Sadly that tag is not supported by GitLab and
> GitHub. But well, "Resolves" is and also a bit more humble if you ask
> me. How
e tracking can also be
> done but the ticket will not be closed and a manual operation will be
> needed.
We will soon gain this ability on bugzilla.kernel.org as one of the features
of the bugbot integration tool (which is still WIP). So, if it helps, I
support making this a recognized trailer.
Acked-by: Konstantin Ryabitsev
-K
On Fri, Jan 20, 2023 at 09:09:18AM +0200, Jani Nikula wrote:
>
> Konstantin?
Sorry, I didn't mean to scholz you around. The pr-tracker-bot is very much a
bespoke solution for Linus, so adapting it to other subsystems is not very
trivial, which is why I've been sitting on this request without any
On Thu, Jan 05, 2023 at 01:35:37PM +0100, Daniel Vetter wrote:
> > Yeah, without the cover letter if you've just got an individual patch it
> > can be unclear what's going on with dependencies and so on for getting
> > the patches merged.
>
> +1 on including the cover letter for any recipient. If
On Thu, Dec 01, 2022 at 02:34:41PM +0100, Javier Martinez Canillas wrote:
> >> Konstantin,
> >>
> >> Can you add a rule in b4 to exclude sta...@vger.kernel.org
> >> (sta...@kernel.org as well?) from getting the whole patchset?
> >
> > sta...@kernel.org is a pipe to /dev/null so that's not needed
On Tue, Nov 22, 2022 at 10:10:47PM +0100, Noralf Trønnes wrote:
> Konstantin found a workaround, so I was able to push the patches.
Yes, this uncovered quite a few bugs -- which is excellent for me, not so
excellent for you. :)
> Here's the result if anyone is interested in seeing the result of
On Tue, Nov 22, 2022 at 06:42:19PM +0100, Noralf Trønnes wrote:
> The first thing that strikes me is that everyone mentioned in one of the
> patches get the entire patchset, even sta...@vger.kernel.org (cc'ed in a
> fixes patch). The first patch touches a core file and as a result a few
> drivers,
On Mon, Nov 21, 2022 at 07:13:28PM +0100, Noralf Trønnes wrote:
> > Otherwise, you might consider using:
> > https://b4.docs.kernel.org/en/latest/contributor/send.html#authenticating-with-the-web-submission-endpoint
> >
>
> That's an interesting option. I did briefly look at b4 a few months back
On Thu, Sep 22, 2022 at 02:51:00PM +0200, Krzysztof Kozlowski wrote:
> Thanks for explanation! Probably your patches are perfectly fine and
> should apply, although I must admit diffstat is often useful.
Krzysztof:
The patches should indeed apply without problems and there's a fix for the
On Mon, Aug 29, 2022 at 08:46:42PM +0200, Noralf Trønnes wrote:
> Something has gone wrong with this patchset, there are double line endings.
I noticed this, too, and I think the reason is because these patches were
generated with "b4 send -o", but actually sent using git-send-email. It's not
a
On Wed, Nov 14, 2018 at 12:57:03PM +0200, Jani Nikula wrote:
> Hey, this is pretty nice! Thanks!
>
> For whatever reason, two copies were sent, though:
>
>
14 matches
Mail list logo
