All of lore.kernel.org
 help / color / mirror / Atom feed
From: "kilian.zinnecker--- via buildroot" <buildroot@buildroot.org>
To: kilian.zinnecker@mail.de, buildroot@buildroot.org
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Robert Nelson <robertcnelson@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH v2 1/2] package/xuantie-bins: new package
Date: Sat, 10 Feb 2024 16:22:10 +0100	[thread overview]
Message-ID: <4544153.LvFx2qVVIh@laptop> (raw)
In-Reply-To: <08b6187c-94f2-4cbc-b0e8-0066ca687796@benettiengineering.com>

Hello Giulio, all,

> Hi Yegor, Kilian,

This is strange, maybe someone can have a look here: On ozlabs, there are a 
lot of patches, which have the submitter "kilian.zinnecker--- via buildroot". 
However, most of them are NOT from me. E.g., one from Yegor Yefremov [1] is 
marked with submitter "kilian.zinnecker--- via buildroot" - However, I am 
definitively not Yegor, and none of his patches is from me. There are even more 
patches marked with "kilian.zinnecker--- via buildroot" [2], some of them even 
from before I ever submitted my first patch (the Rock5B board support) to 
buildroot. Does anyone have any idea what this is about, or can have a deeper 
look at this? (The BeagleV-Ahead patches are from me.)

[1] https://patchwork.ozlabs.org/project/buildroot/patch/
20240206132051.2838897-1-yegorslists@googlemail.com/

[2] https://patchwork.ozlabs.org/project/buildroot/list/?
submitter=82609&archive=both&state=*

[--SNIP--]

Thanks for your review Giulio. I will try to address the issues and prepare a 
new version of the patches.

Best regards,
Kilian





_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-02-10 15:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04 23:12 [Buildroot] [PATCH v2 0/2] Add board support for the BeagleV-Ahead kilian.zinnecker--- via buildroot
2023-12-04 23:12 ` [Buildroot] [PATCH v2 1/2] package/xuantie-bins: new package kilian.zinnecker--- via buildroot
2024-02-06 16:56   ` Giulio Benetti
2024-02-10 15:22     ` kilian.zinnecker--- via buildroot [this message]
2024-02-11 12:38       ` Thomas Petazzoni via buildroot
2024-02-11 12:15     ` kilian.zinnecker--- via buildroot
2024-02-13 18:19       ` Giulio Benetti
2023-12-04 23:12 ` [Buildroot] [PATCH v2 2/2] configs/beaglev_ahead: new defconfig kilian.zinnecker--- via buildroot
2024-02-06 16:31   ` Giulio Benetti
2024-02-11 12:24     ` kilian.zinnecker--- via buildroot
2024-02-13 18:17       ` Giulio Benetti

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=4544153.LvFx2qVVIh@laptop \
    --to=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=kilian.zinnecker@mail.de \
    --cc=robertcnelson@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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.