List for cgit developers and users
 help / color / mirror / Atom feed
From: elijah at elijahlynn.net (Elijah Lynn)
Subject: Git blame support
Date: Wed, 21 Jan 2015 16:36:46 -0500	[thread overview]
Message-ID: <CAJ9KuXziQLkNrrO8vYLtb0OaboOdZkfeyg4AEUpr+1LU5uc7JA@mail.gmail.com> (raw)
In-Reply-To: <20150121200150.GB8026@serenity.lan>

Thank you very much John!

I just found a reference on Drupal.org <https://www.drupal.org/node/2285061>
to a 1.0 roadmap posted by Jason A. Donenfeld and he mentioned he would
like to see Git Blame support by then.

http://article.gmane.org/gmane.comp.version-control.cgit/2030/match=blame

Jason, do you know if work has been started on this? I am also wondering
how the cgit community would react to some kind of chipin to fund
development time towards this?

Thanks,


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


On Wed, Jan 21, 2015 at 3:01 PM, John Keeping <john at keeping.me.uk> wrote:

> On Wed, Jan 21, 2015 at 11:02:32AM -0500, Elijah Lynn wrote:
> > I am not sure if there is an issue tracker being used for the project. I
> > asked the list a while back but haven't heard back. At any rate, is
> there a
> > way I can see if there is git blame support being built? I am part of the
> > Drupal community and there may be some of us who could help it along if
> it
> > is planned.
>
> I'm not aware of anyone working on blame support.  Having taken a quick
> look, Git does most of the work in builtin/blame.c so it won't be
> possible to easily re-use any of that code, which means it's not a small
> task to add blame support.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20150121/235dac19/attachment.html>


      reply	other threads:[~2015-01-21 21:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21 16:02 elijah
2015-01-21 20:01 ` john
2015-01-21 21:36   ` 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=CAJ9KuXziQLkNrrO8vYLtb0OaboOdZkfeyg4AEUpr+1LU5uc7JA@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).