emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: Uwe Brauer <oub@mat.ucm.es>, emacs-orgmode@gnu.org
Subject: Re: ChangeLog.org
Date: Fri, 22 Jul 2022 17:05:03 +0200	[thread overview]
Message-ID: <87edydw5ls.fsf@mat.ucm.es> (raw)
In-Reply-To: 87sfmtg01f.fsf@web.de

[-- Attachment #1: Type: text/plain, Size: 989 bytes --]

>>> "AB" == Arne Babenhauserheide <arne_bab@web.de> writes:

> Uwe Brauer <oub@mat.ucm.es> writes:

>> So the question is, how to generate this file. Maybe there is a
>> ChangeLog--> ChangeLog.org exporter/converter?
>> https://github.com/johnlepikhin/el-conventional-changelog/blob/master/conventional-changelog.el

> I see only 6 calls to git in that file. Maybe the easiest way would be
> to port it?

Well looking more in the code, it seems that the logic is

    1. Commit with commit message

    2. Then extract and insert that commit message into a org buffer
       respecting org syntax

This is not what I am looking for. My workflow is, usually, the other
way around.

    1. I add an entry to the ChangeLog file

    2. Then I commit this message gets inserted (this step wouldn't make
       much sense if ChangeLog file uses org syntax, I admit)

But I want an independent ChangeLog file not an extracting from my
commit messages.


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

      reply	other threads:[~2022-07-22 15:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21 16:03 ChangeLog.org Uwe Brauer
2022-07-21 17:56 ` ChangeLog.org Fraga, Eric
2022-07-22  4:53   ` ChangeLog.org Uwe Brauer
2022-07-22  5:53     ` ChangeLog.org Dr. Arne Babenhauserheide
2022-07-22 15:05       ` Uwe Brauer [this message]

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87edydw5ls.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=arne_bab@web.de \
    --cc=emacs-orgmode@gnu.org \


* 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.
Code repositories for project(s) associated with this public inbox


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 read-only IMAP folder(s) and NNTP newsgroup(s).