discussion and development of piem
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Kyle Meyer <kyle@kyleam.com>
Cc: piem@inbox.kyleam.com
Subject: Re: [PATCH] New customization: `piem-default-branch-prefix'
Date: Sun, 30 Apr 2023 20:11:39 +0000	[thread overview]
Message-ID: <87sfchyvt0.fsf@localhost> (raw)
In-Reply-To: <87pm7ljhc1.fsf@kyleam.com>

Kyle Meyer <kyle@kyleam.com> writes:

> Thanks, but I'd prefer not to add an option for this case.  It's
> straightforward for users that want to add a prefix to do so by defining
> a light wrapper around piem-name-branch-who-what-v and pointing
> piem-default-branch-function to it.

Sure. That's what I am doing now. Just thought that it might be a fairly
common need, and having customization would serve as a reminder about
such possibility.

Your call though, indeed.

Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

      reply	other threads:[~2023-04-30 20:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-30 12:45 [PATCH] New customization: `piem-default-branch-prefix' Ihor Radchenko
2023-04-30 19:33 ` Kyle Meyer
2023-04-30 20:11   ` Ihor Radchenko [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://git.kyleam.com/

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

  git send-email \
    --in-reply-to=87sfchyvt0.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.com \


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