From: Uwe Brauer <oub@mat.ucm.es>
To: Theodor Thornhill <theo@thornhill.no>
Cc: Uwe Brauer <oub@mat.ucm.es>, emacs-devel@gnu.org
Subject: Re: [ELPA] package proposal: fannypack.el
Date: Thu, 24 Feb 2022 08:04:46 +0100 [thread overview]
Message-ID: <8735k8219t.fsf@mat.ucm.es> (raw)
In-Reply-To: df90ac7b-06d2-408b-8d79-bf3bcacc22c5@email.android.com
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
>>> "TT" == Theodor Thornhill <theo@thornhill.no> writes:
> Very interesting, but that is GIT only? No change for mercurial?
> Because this is a feature I miss very much.
> I didn't get to that yet, but I will add it! Would hg bookmarks be
> sufficient, or should i use both branch and bookmarks? I'm sure vc
> exposes what I want, so I will look into it :)
Thanks for your quick reply.
I don't use bookmarks, only named branches (this is why I use mercurial
and not git 😉).
On the other there is a new feature called topics which is the ideal
combination of mercurial named branches and well git branches (you can
delete them but each change set/commit gets a tag when active).
This however is still not in core mercurial but you need the evolve
extension enabled.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2022-02-24 7:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 13:24 [ELPA] package proposal: fannypack.el Theodor Thornhill
2022-02-22 19:11 ` Philip Kaludercic
2022-02-22 19:40 ` Theodor Thornhill
2022-02-22 20:02 ` Philip Kaludercic
2022-02-22 21:11 ` Theodor Thornhill
2022-02-22 21:16 ` Bob Rogers
2022-02-22 21:29 ` Theodor Thornhill
2022-02-22 21:41 ` Stefan Monnier
2022-02-22 22:24 ` Theodor Thornhill
2022-02-24 4:50 ` Richard Stallman
2022-02-24 6:14 ` Theodor Thornhill
2022-02-24 6:30 ` Uwe Brauer
2022-02-24 6:43 ` Theodor Thornhill
2022-02-24 7:04 ` Uwe Brauer [this message]
2022-02-24 7:28 ` Theodor Thornhill
2022-02-24 7:41 ` 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:
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=8735k8219t.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=emacs-devel@gnu.org \
--cc=theo@thornhill.no \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.