aboutsummaryrefslogtreecommitdiffstats
path: root/.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/c283cbb1-2964-4372-9d9c-117dd3a85518/comments/d7ce9255-a1d2-4ddf-85ba-6319ac97aae7
diff options
context:
space:
mode:
authorW. Trevor King <wking@tremily.us>2012-09-03 09:01:57 -0400
committerW. Trevor King <wking@tremily.us>2012-09-03 09:01:57 -0400
commit274725245f069882af2a62c49382353043bb9caf (patch)
treeadf63d4b71fa59ea81a177c83d97c37eaa771d8e /.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/c283cbb1-2964-4372-9d9c-117dd3a85518/comments/d7ce9255-a1d2-4ddf-85ba-6319ac97aae7
parentccf367f1a82035686323828669db1ad3afc4043a (diff)
downloadbugseverywhere-274725245f069882af2a62c49382353043bb9caf.tar.gz
bea/c283cb: merge earlier hosting-integration emails onto gitorious-issues bug.
Diffstat (limited to '.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/c283cbb1-2964-4372-9d9c-117dd3a85518/comments/d7ce9255-a1d2-4ddf-85ba-6319ac97aae7')
-rw-r--r--.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/c283cbb1-2964-4372-9d9c-117dd3a85518/comments/d7ce9255-a1d2-4ddf-85ba-6319ac97aae7/body16
-rw-r--r--.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/c283cbb1-2964-4372-9d9c-117dd3a85518/comments/d7ce9255-a1d2-4ddf-85ba-6319ac97aae7/values14
2 files changed, 30 insertions, 0 deletions
diff --git a/.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/c283cbb1-2964-4372-9d9c-117dd3a85518/comments/d7ce9255-a1d2-4ddf-85ba-6319ac97aae7/body b/.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/c283cbb1-2964-4372-9d9c-117dd3a85518/comments/d7ce9255-a1d2-4ddf-85ba-6319ac97aae7/body
new file mode 100644
index 0000000..eb013a4
--- /dev/null
+++ b/.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/c283cbb1-2964-4372-9d9c-117dd3a85518/comments/d7ce9255-a1d2-4ddf-85ba-6319ac97aae7/body
@@ -0,0 +1,16 @@
+On Thu, Mar 18, 2010 at 05:02:13PM -0400, Chris Ball wrote:
+> The fact that gitorious is written in Ruby on Rails probably makes the
+> idea of using gitorious in particular a non-starter, but I thought I'd
+> throw it out there.
+> ...
+> (One way to get around the Ruby/Python problem would be to have the
+> bugtracker simply operate independently from the rest of the site,
+> which I suppose would work fine but wouldn't be elegant to use.)
+
+Another option would be to drive BE in a subprocess via Ruby's IO.popen.
+A proof-of-concept implementation could use our standard `be' command.
+A production implementation could be either of
+ * multi-command BE interface to avoid repeaded repository reloads
+ (may be too man process or too much memory for the server)
+ * better BE caching for faster reloads
+ (more work for us ;)
diff --git a/.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/c283cbb1-2964-4372-9d9c-117dd3a85518/comments/d7ce9255-a1d2-4ddf-85ba-6319ac97aae7/values b/.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/c283cbb1-2964-4372-9d9c-117dd3a85518/comments/d7ce9255-a1d2-4ddf-85ba-6319ac97aae7/values
new file mode 100644
index 0000000..553cb46
--- /dev/null
+++ b/.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/c283cbb1-2964-4372-9d9c-117dd3a85518/comments/d7ce9255-a1d2-4ddf-85ba-6319ac97aae7/values
@@ -0,0 +1,14 @@
+Alt-id: <20100319120053.GA20225@mjolnir.hsd1.nj.comcast.net>
+
+
+Author: '"W. Trevor King" <wking@drexel.edu>'
+
+
+Content-type: text/plain
+
+
+Date: Fri, 19 Mar 2010 12:00:53 +0000
+
+
+In-reply-to: <m3634ttkbu.fsf@pullcord.laptop.org>
+