public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: Xiao Yang <yangx.jy@cn.fujitsu.com>,
	Richard Palethorpe <rpalethorpe@suse.com>,
	ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 0/5] Release scripts and docs
Date: Tue, 26 Sep 2023 14:22:42 +0200	[thread overview]
Message-ID: <ZRLNEoMr2OpKhcfi@yuki> (raw)
In-Reply-To: <20230922161304.GA587441@pevik>

Hi!
> BTW the changelog skeleton should be separated to be useful (Cyril does it).

I do not think that we can ever automate the changelog creation, it's
manual process that requires reading patch description for all the
patches, understanding what is there and writing down something based on
that. Even the credits section usually needs some hand fixes, since
there are typos, different emails and so on in the git tags.

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2023-09-26 12:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20  9:53 [LTP] [PATCH 0/5] Release scripts and docs Petr Vorel
2023-09-20  9:53 ` [LTP] [PATCH 1/5] tools: Add a script for tagging the release Petr Vorel
2023-09-20  9:53 ` [LTP] [PATCH 2/5] tools: Add script for creating tarballs and metadata Petr Vorel
2023-09-20  9:53 ` [LTP] [PATCH 3/5] doc: Rename files to names from ltp.wiki.git Petr Vorel
2023-09-26 11:47   ` Cyril Hrubis
2023-09-20  9:53 ` [LTP] [PATCH 4/5] doc: Add Release procedure Petr Vorel
2023-09-26 11:46   ` Cyril Hrubis
2023-09-26 13:39     ` Petr Vorel
2023-09-20  9:53 ` [LTP] [PATCH 5/5] doc: Update release procedure Petr Vorel
2023-09-20 15:29   ` Petr Vorel
2023-09-20 15:39   ` Petr Vorel
2023-09-24  0:35   ` Li Wang
2023-09-24 21:14     ` Petr Vorel
2023-09-25  2:31       ` Li Wang
2023-09-25 12:50         ` Petr Vorel
2023-09-27  6:44           ` Petr Vorel
2023-09-26 12:14   ` Cyril Hrubis
2023-09-26 13:54     ` Petr Vorel
2023-09-26 14:23       ` Cyril Hrubis
2023-09-26 15:29         ` Petr Vorel
2023-09-21  8:18 ` [LTP] [PATCH 0/5] Release scripts and docs Li Wang
2023-09-21  8:43   ` Jan Stancek
2023-09-22 16:13     ` Petr Vorel
2023-09-26 12:22       ` Cyril Hrubis [this message]
2023-09-26 13:46         ` Petr Vorel
2023-09-26 13:48           ` Cyril Hrubis
2023-09-26 12:16     ` Cyril Hrubis
2023-09-26 13:41       ` Petr Vorel

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=ZRLNEoMr2OpKhcfi@yuki \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    --cc=rpalethorpe@suse.com \
    --cc=yangx.jy@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox