List for cgit developers and users
 help / color / mirror / Atom feed
From: kevin at scrye.com (Kevin Fenzi)
Subject: highlight css ?
Date: Sun, 13 Apr 2014 15:58:25 -0600	[thread overview]
Message-ID: <20140413155825.43b191e5@voldemort.scrye.com> (raw)
In-Reply-To: <5341A7B8.1060504@hupie.com>

On Sun, 06 Apr 2014 21:15:04 +0200
Ferry Huberts <mailings at hupie.com> wrote:

(sorry for delay in reply, it's been a crazy week.)

> create an rpm with a 'trigger' that does just that on install/update
> of the cgit package status.
> I've done that before for other things.

Yeah, triggers are kind of nasty, and I would like to avoid them. 

I don't guess there is any good/simple solution here... 

kevin
--
> 
> On 06/04/14 20:08, Kevin Fenzi wrote:
> > Greetings.
> >
> > Some folks like to adjust the css that highlight uses, and do so by
> > doing:
> >
> > highlight --print-style --style-outfile=stdout >> cgit.css
> >
> > and then adjusting, but then cgit.css changes on upgrades back to
> > the stock cgit one.
> >
> > See:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1078949
> >
> > For downstream bug.
> >
> > Any ideas for how to gracefully handle this use case?
> >
> > kevin
> >
> >
> >
> > _______________________________________________
> > CGit mailing list
> > CGit at lists.zx2c4.com
> > http://lists.zx2c4.com/mailman/listinfo/cgit
> >
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20140413/11a8aea8/attachment.asc>


      reply	other threads:[~2014-04-13 21:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-06 18:08 kevin
2014-04-06 19:15 ` mailings
2014-04-13 21:58   ` kevin [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=20140413155825.43b191e5@voldemort.scrye.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).