From: Jonathan Nieder <jrnieder@gmail.com>
To: git@vger.kernel.org
Subject: [ANNOUNCE] Bug tracker for Git
Date: Wed, 22 Nov 2017 17:12:27 -0800 [thread overview]
Message-ID: <20171123011227.GM11671@aiede.mtv.corp.google.com> (raw)
Hi,
As discussed at [1], I've occasionally wanted to have a place to keep
track of bugs I'm working on in Git. Some kind people on the Chromium
project helped me set an issue tracker up, so now we have one.
https://crbug.com/git
Feel free to file bugs, feature requests, and leftover bits there.
I'll be happy to triage them to keep the list of bugs meaningful.
Anyone else wanting to help with bug management can feel free to
contact me and I'll grant you permissions to edit issues.
This particular implementation of an issue tracker is Monorail
<https://chromium.googlesource.com/infra/infra/+/master/appengine/monorail>.
It is similar to the issue tracker that used to run at
code.google.com. If you find things you don't like about the way it
works, they accept patches. :)
It accepts replies to the emails it sends.
This uses Google accounts to authenticate people filing a bug. If you
would like a Google account for your existing email address, you can
get one at https://accounts.google.com/SignUpWithoutGmail.
There is an API for programmatic access to the issue tracker: [2].
One thing I would appreciate help with is using that API to make
regular backups. The chromium project has their own backups using
database dumps but I would be happier if multiple people are making
backups independently.
This is an experiment --- I don't know whether it will stick. The
configuration will likely change as we get experience with it. I
expect to be using it to track my own work for the forseeable future.
I'd be happy if it is useful to others as well.
Thanks,
Jonathan
[1] https://public-inbox.org/git/20170919160753.GA75068@aiede.mtv.corp.google.com/
https://public-inbox.org/git/vpqiovpubmh.fsf@anie.imag.fr/
https://public-inbox.org/git/7vhay9tqs6.fsf@alter.siamese.dyndns.org/
https://public-inbox.org/git/7vehzjugdz.fsf@alter.siamese.dyndns.org/
https://public-inbox.org/git/4A1FB1DE.3070904@op5.se/
[2] https://chromium.googlesource.com/infra/infra/+/master/appengine/monorail/doc/api.md
reply other threads:[~2017-11-23 1:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171123011227.GM11671@aiede.mtv.corp.google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).