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

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

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?

Or even better: generalize it by calling (vc-deduce-backend) and
automatically using the commands for the found vcs (and sending a patch
to the author)?

Best wishes,
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]

  reply	other threads:[~2022-07-22  6:02 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     ` Dr. Arne Babenhauserheide [this message]
2022-07-22 15:05       ` ChangeLog.org Uwe Brauer

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=87sfmtg01f.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=oub@mat.ucm.es \


* 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).