public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: dwarves@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	bpf@vger.kernel.org, Alan Maguire <alan.maguire@oracle.com>,
	Jiri Olsa <jolsa@kernel.org>, Jan Engelhardt <jengelh@inai.de>,
	Matthias Schwarzott <zzam@gentoo.org>,
	Viktor Malik <vmalik@redhat.com>,
	Eduard Zingerman <eddyz87@gmail.com>,
	Jan Alexander Steffens <heftig@archlinux.org>,
	Domenico Andreoli <cavok@debian.org>,
	Dominique Leuenberger <dimstar@opensuse.org>,
	Daniel Xu <dxu@dxuuu.xyz>,
	Yonghong Song <yonghong.song@linux.dev>
Subject: Re: ANNOUNCE: pahole v1.27 (reproducible builds, BTF kfuncs)
Date: Tue, 11 Jun 2024 19:52:12 -0300	[thread overview]
Message-ID: <ZmjVHKLTP4_hnzug@x1> (raw)
In-Reply-To: <ZmjDuv_zuhA3Xp2m@codewreck.org>

On Wed, Jun 12, 2024 at 06:38:02AM +0900, Dominique Martinet wrote:
> It looks like the v1.27 tag has not been pushed to the git repos (either
> this or github), we're using git snapshots for nixpkgs, so it'd be great
> if a tag could be pushed out.

Done.

https://git.kernel.org/pub/scm/devel/pahole/pahole.git/tag/?h=v1.27
https://github.com/acmel/dwarves/releases/tag/v1.27

> (I think some release monitoring tools left and right also use tags,
> even if that's less important if you Cc other distro maintainers... I
> just happened to see the mail on bpf@vger.)

May I add your e-mail here:

acme@x1:~/git/pahole$ cat PKG-MAINTAINERS 
# Please let me know if I should remove/update/add more distro package maintainers here
# I'm keeping this so that I CC them when releasing new versions, thanks!

Jan Alexander Steffens <heftig@archlinux.org>
Domenico Andreoli <cavok@debian.org>
Matthias Schwarzott <zzam@gentoo.org>
Dominique Leuenberger <dimstar@opensuse.org>
acme@x1:~/git/pahole$

So that on the next release I CC you?

Thanks for reporting!

- Arnaldo

  reply	other threads:[~2024-06-11 22:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11 21:26 ANNOUNCE: pahole v1.27 (reproducible builds, BTF kfuncs) Arnaldo Carvalho de Melo
2024-06-11 21:38 ` Dominique Martinet
2024-06-11 22:52   ` Arnaldo Carvalho de Melo [this message]
2024-06-11 23:46     ` Dominique Martinet
2024-06-12 10:07 ` Matthias Schwarzott
2024-06-14 19:09   ` Arnaldo Carvalho de Melo
2024-06-13 21:40 ` Nathan Chancellor
2024-06-17 19:39   ` Arnaldo Carvalho de Melo
2024-06-17 20:02     ` [PATCH/RFT] " Arnaldo Carvalho de Melo
2024-06-17 21:08       ` Nathan Chancellor
2024-06-18 13:51         ` Arnaldo Carvalho de Melo
2024-06-18 14:30           ` [PATCH fyi 1/1] dwarf_loader: Add missing cus__add(cus, cu) to cus__merge_and_process_cu() Arnaldo Carvalho de Melo
2024-07-10 19:31           ` [PATCH/RFT] Re: ANNOUNCE: pahole v1.27 (reproducible builds, BTF kfuncs) Nathan Chancellor

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=ZmjVHKLTP4_hnzug@x1 \
    --to=acme@kernel.org \
    --cc=alan.maguire@oracle.com \
    --cc=asmadeus@codewreck.org \
    --cc=bpf@vger.kernel.org \
    --cc=cavok@debian.org \
    --cc=dimstar@opensuse.org \
    --cc=dwarves@vger.kernel.org \
    --cc=dxu@dxuuu.xyz \
    --cc=eddyz87@gmail.com \
    --cc=heftig@archlinux.org \
    --cc=jengelh@inai.de \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vmalik@redhat.com \
    --cc=yonghong.song@linux.dev \
    --cc=zzam@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox