List for cgit developers and users
 help / color / mirror / Atom feed
From: elijah at elijahlynn.net (Elijah Lynn)
Subject: Issue tracker? Bountysource
Date: Wed, 10 Sep 2014 13:22:22 -0400	[thread overview]
Message-ID: <CAJ9KuXwY_p9mhdp_sPKLQrmwEL0+wHHt+xU8V6brpn4fqYO6vg@mail.gmail.com> (raw)
In-Reply-To: <CAJ9KuXys0VU8W3BGVHh3iSMszDDg9p6Y_z2gDn1ZBzm+2txU6Q@mail.gmail.com>

I forgot to mention that there is a Bountysource page for cgit here =>
https://www.bountysource.com/trackers/3296804-cgit


Elijah Lynn
www.elijahlynn.net
903.Eli.jahs (354.5247)


On Wed, Sep 10, 2014 at 1:19 PM, Elijah Lynn <elijah at elijahlynn.net> wrote:

> Hi,
>
> I was wondering if there was an issue tracker or if just the mailing list
> is used for tracking issues?
>
> My main motivation is that Drupal just adopted cgit and one feature we
> really miss is git blame (https://www.drupal.org/node/2285061). I am
> aware it is on the cgit roadmap for a 1.0 release (
> http://article.gmane.org/gmane.comp.version-control.cgit/2030/match=blame)
> and I want to know if there is anything our community can help do to speed
> that up.
>
> I just went to Bountysource.com to try to setup a bounty for this but it
> turns out a project needs and official issue tracker. The one on Github (
> https://github.com/qznc/cgit) appears to just be a mirror and not
> official. I asked what issue trackers are supported on #bountysource in
> Freenode and:
>
>     "scalability-junk> elijah: supported afaik are bugzilla, jira, github
> and a few more."
>
> Anyways, I didn't see an issue tracker so I thought I would ask. I would
> love to setup a bounty to get git blame support worked on. Or if there is
> anything else we could do please let me know or post a response in the
> Drupal issue mentioned above.
>
> Cheers,
>
> Elijah Lynn
> www.elijahlynn.net
> 903.Eli.jahs (354.5247)
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20140910/618e50a4/attachment.html>


      reply	other threads:[~2014-09-10 17:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-10 17:19 elijah
2014-09-10 17:22 ` elijah [this message]

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=CAJ9KuXwY_p9mhdp_sPKLQrmwEL0+wHHt+xU8V6brpn4fqYO6vg@mail.gmail.com \
    --to=cgit@lists.zx2c4.com \
    /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 NNTP newsgroup(s).