List for cgit developers and users
 help / color / mirror / Atom feed
From: stefan.naewe at gmail.com (Stefan Naewe)
Subject: [PATCH] ui-commit: display commit notes as 'raw'
Date: Sat, 21 Mar 2015 16:37:39 +0100	[thread overview]
Message-ID: <CAJzBP5RcgJ-=Z3zoDDVENBWgR9t-+QS9d8ZNsRnqotE7k0+Gtw@mail.gmail.com> (raw)
In-Reply-To: <20150321131938.GB1344@serenity>

On Sat, Mar 21, 2015 at 2:19 PM, John Keeping <john at keeping.me.uk> wrote:
> On Sat, Mar 21, 2015 at 02:11:51PM +0100, Stefan Naewe wrote:
>> On Fri, Mar 20, 2015 at 10:29 PM, John Keeping <john at keeping.me.uk> wrote:
>> > On Fri, Mar 20, 2015 at 05:39:53PM +0100, Stefan Naewe wrote:
>> >> When the git function format_display_notes() is called
>> >> with a value != 0 as the last argument ('raw') the notes text
>> >> gets displayed w/o an additional 'Notes:' header. This seems
>> >> to be better suited for our needs since we're already displaying
>> >> a similar header.
>> >
>> > What happens when there are multiple display notes refs?  It seems that
>> > without "raw", format_note() puts the name of the ref in the header it
>> > prints (if it's not the default notes ref).
>> That's true for 'git show --notes=...' for example.
>>
>> But how would you specify the name of the notes ref in cgit ?
>
> git config --add notes.displayRef ...

Thanks. That looks like attached. One without and one with my patch.

Maybe we should drop the "Notes" headline that cgit generates, instead ?

Stefan
-- 
----------------------------------------------------------------
python -c "print '73746566616e2e6e6165776540676d61696c2e636f6d'.decode('hex')"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: shot-cgit-notes-2refs.png
Type: image/png
Size: 10328 bytes
Desc: not available
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20150321/345b5498/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: shot-cgit-notes-2refs-raw.png
Type: image/png
Size: 6340 bytes
Desc: not available
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20150321/345b5498/attachment-0001.png>


      reply	other threads:[~2015-03-21 15:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20 16:39 stefan.naewe
2015-03-20 21:29 ` john
2015-03-21 13:11   ` stefan.naewe
2015-03-21 13:19     ` john
2015-03-21 15:37       ` stefan.naewe [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='CAJzBP5RcgJ-=Z3zoDDVENBWgR9t-+QS9d8ZNsRnqotE7k0+Gtw@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).