List for cgit developers and users
 help / color / mirror / Atom feed
From: john at keeping.me.uk (John Keeping)
Subject: [PATCH] ui-commit: display commit notes as 'raw'
Date: Sat, 21 Mar 2015 13:19:38 +0000	[thread overview]
Message-ID: <20150321131938.GB1344@serenity> (raw)
In-Reply-To: <CAJzBP5SA8fQKsVbLkdPOPyiBGJdWaXT06VSZ6iyfxFPdM8L-XA@mail.gmail.com>

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 ...

> > It's possible that the correct answer is that we don't care about that
> > case, but it is potentially a regression for people who want to display
> > multiple notes.
> 
> Attached are two screenshots of commit notes added with 'git notes
> add..' for the first line and
> 'git notes append...' for the second line. That particular commit also
> has another note
> attached in the 'refs/notes/todo' namespace.
> 
> My opinion about this topic: I really like the way cgit displays the
> commit notes but not the
> double "Notes" header line.


  reply	other threads:[~2015-03-21 13:19 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 [this message]
2015-03-21 15:37       ` stefan.naewe

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=20150321131938.GB1344@serenity \
    --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).