From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: [PATCH 0/3] Blame UI
Date: Wed, 12 Aug 2015 17:07:12 +0200 [thread overview]
Message-ID: <CAHmME9oieyjGq0VjBFTnHezVHxgftTSBTA0HQ7sES-tviAe-bw@mail.gmail.com> (raw)
In-Reply-To: <20150812150258.GJ30507@serenity.lan>
Relying on an installed git does impose an additional deployment
requirement we didn't have before. Previously git was just required
for running the tests (developers), but not for deployment.
I'll wait to receive some other opinions on the topic of relying on
having the executables around.
Alternatively - any chance of working with upstream to make it a more
generic interface?
next prev parent reply other threads:[~2015-08-12 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 13:03 john
2015-08-12 13:03 ` [PATCH 1/3] ui-blame: add blame UI john
2015-08-12 13:03 ` [PATCH 2/3] ui-shared: add cgit_blame_link() john
2015-08-12 13:03 ` [PATCH 3/3] ui-tree: generate blame links john
2015-08-12 13:44 ` [PATCH 0/3] Blame UI Jason
2015-08-12 15:02 ` john
2015-08-12 15:07 ` Jason [this message]
2015-08-12 15:26 ` john
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=CAHmME9oieyjGq0VjBFTnHezVHxgftTSBTA0HQ7sES-tviAe-bw@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).