From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Jiri Olsa <jolsa@redhat.com>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
users@linux.kernel.org
Subject: Re: [RFC] tools lib traceevent: How to do library versioning being in the Linux kernel source?
Date: Mon, 6 Jan 2020 15:14:01 -0500 [thread overview]
Message-ID: <20200106201401.hcneggg4xmoazr5e@chatter.i7.local> (raw)
In-Reply-To: <20200106194711.GC11285@kernel.org>
On Mon, Jan 06, 2020 at 04:47:11PM -0300, Arnaldo Carvalho de Melo wrote:
> Sure, regardless of where you do source code control you will need to
> tag, create a tarball, signatures (which kup helps with) for kernel.org,
> for instance I use:
>
> kup put perf-${VER}.tar.xz perf-${VER}.tar.sign /pub/linux/kernel/tools/perf/v${VER}/perf-${VER}.tar.xz
It's worth noting that you don't have to use kup if you don't want to --
we have a mechanism to create tarball releases directly from tag
signatures. You just have to add a special note to the tag and the
backend does the rest automatically -- we have a handy script [^1] to
make it easier.
Greg KH has been using this process for a while now.
If you would like to switch to that instead of using kup directly, just
let me know.
-K
[^1]: https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git/tree/git-archive-signer
next prev parent reply other threads:[~2020-01-06 20:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 17:20 [RFC] tools lib traceevent: How to do library versioning being in the Linux kernel source? Steven Rostedt
2020-01-02 18:42 ` Arnaldo Carvalho de Melo
2020-01-02 23:46 ` Steven Rostedt
2020-01-02 22:43 ` Sudip Mukherjee
2020-01-03 23:19 ` Steven Rostedt
2020-01-07 13:15 ` Namhyung Kim
2020-01-02 23:49 ` Jiri Olsa
2020-01-02 23:58 ` Steven Rostedt
2020-01-03 0:09 ` Sudip Mukherjee
2020-01-03 13:36 ` Jiri Olsa
2020-01-03 18:29 ` Sudip Mukherjee
2020-01-03 23:16 ` Steven Rostedt
2020-01-06 15:19 ` Jiri Olsa
2020-01-06 16:26 ` Arnaldo Carvalho de Melo
2020-01-06 16:36 ` Steven Rostedt
2020-01-06 19:47 ` Arnaldo Carvalho de Melo
2020-01-06 20:14 ` Konstantin Ryabitsev [this message]
2020-01-06 22:00 ` Arnaldo Carvalho de Melo
2020-01-06 20:47 ` [kernel.org users] " Jason Gunthorpe
2020-01-06 20:52 ` Steven Rostedt
2020-01-07 17:44 ` Jason Gunthorpe
2020-01-06 18:22 ` Konstantin Ryabitsev
2020-01-03 12:17 ` Masami Hiramatsu
2020-01-03 23:12 ` Steven Rostedt
2020-01-05 13:18 ` Masami Hiramatsu
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=20200106201401.hcneggg4xmoazr5e@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=arnaldo.melo@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=users@linux.kernel.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;
as well as URLs for NNTP newsgroup(s).