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

Ihor Radchenko writes:

> I'd like to add a new customization that adds a custom prefix string to
> the generated branch names. That way, I can easily see the branches
> generated by piem in the list of branches, nicely grouped when sorting
> alphabetically.

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.

  reply	other threads:[~2023-04-30 19:33 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 [this message]
2023-04-30 20:11   ` Ihor Radchenko

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=87pm7ljhc1.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.com \
    --cc=yantar92@posteo.net \


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