From: Ricardo Wurmus <rekado@elephly.net>
To: Adriano Peluso <randomlooser@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: issue tracking in git
Date: Fri, 13 Aug 2021 15:18:51 +0200 [thread overview]
Message-ID: <87v949iitg.fsf@elephly.net> (raw)
In-Reply-To: <c7c57dde368646593eaa9536c69af74b9fa93790.camel@riseup.net>
Hi Adriano,
> some time ago, in the context of an on line conference about
> Guix,
> someone suggested me that the bitcoin community had run a survey
> about
> available solutions for issue tracking in git
Was it perhaps Carl Dong?
> I don't remember the name of such person and I am wondering if
> amy
> progress has been achieved on that front
I don’t think there was a decision to do issue tracking in git.
Many years ago I used Bugs Everywhere
(https://bugs-everywhere.readthedocs.io/en/latest/) for my
personal projects. I really quite liked it, not least because you
can close a bug right as you fix the issue — it’s part of the same
commit.
I have no idea how well it works when there’s a lot of “traffic”
in a distributed project, e.g. when there are several comments to
the same issue by different people. Having merge conflicts in the
issue tracker is a headache I’d like to avoid.
--
Ricardo
next prev parent reply other threads:[~2021-08-13 13:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 6:29 issue tracking in git Adriano Peluso
2021-08-13 13:18 ` Ricardo Wurmus [this message]
2021-08-13 16:19 ` Giovanni Biscuolo
2021-08-14 8:30 ` Adriano Peluso
2021-08-15 10:39 ` Pjotr Prins
2021-08-15 15:28 ` Giovanni Biscuolo
2022-11-22 17:57 ` Giovanni Biscuolo
2022-11-23 4:35 ` Pjotr Prins
2022-11-23 10:29 ` Giovanni Biscuolo
2022-11-23 10:59 ` indieterminacy
2022-11-23 14:19 ` Giovanni Biscuolo
2022-11-23 16:53 ` indieterminacy
2022-11-23 13:18 ` Pjotr Prins
2022-11-23 14:58 ` Giovanni Biscuolo
2022-11-25 13:45 ` zimoun
2022-11-25 22:03 ` Arun Isaac
2022-11-26 9:51 ` zimoun
2022-11-24 22:01 ` Arun Isaac
2021-08-14 8:29 ` Adriano Peluso
2021-08-13 14:39 ` raingloom
2021-08-16 4:39 ` Adriano Peluso
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=87v949iitg.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=randomlooser@riseup.net \
/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/guix.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.