From: Lele Gaifax <lele@metapensiero.it>
To: help-gnu-emacs@gnu.org
Subject: Re: How to streamline my Magit workflow?
Date: Sat, 29 Oct 2022 13:18:49 +0200 [thread overview]
Message-ID: <87v8o227za.fsf@metapensiero.it> (raw)
In-Reply-To: 87bkpvqdmh.fsf@mbork.pl
Hi Marcin,
never used, and maybe known to you already, but isn't this fulfilled by (or
buildable on top of) the Magit's Forge extension
(https://magit.vc/manual/forge/index.html)? It seems to (partially?)
support Bitbucket.
ciao, lele.
--
nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia.
lele@metapensiero.it | -- Fortunato Depero, 1929.
next prev parent reply other threads:[~2022-10-29 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 7:43 How to streamline my Magit workflow? Marcin Borkowski
2022-10-29 11:18 ` Lele Gaifax [this message]
2022-10-29 17:03 ` Kyle Meyer
2022-10-29 17:15 ` Björn Bidar
2022-10-30 5:28 ` Peter Hardy
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8o227za.fsf@metapensiero.it \
--to=lele@metapensiero.it \
--cc=help-gnu-emacs@gnu.org \
/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.
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).