From: "Eric Schulte" <schulte.eric@gmail.com>
To: "Michaël Parienti" <michael@parienti.name>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: blorgit build
Date: Sun, 17 Oct 2010 12:48:15 -0600 [thread overview]
Message-ID: <87sk047j0w.fsf@gmail.com> (raw)
In-Reply-To: <20101017154046.29b6c7ce@micha.parienti.lan> ("Michaël Parienti"'s message of "Sun, 17 Oct 2010 15:40:46 +0200")
Hi,
I've fixed these issues, a classic bitrot situation due to breaking
changes in upstream requirements. After pulling down the latest from
git and updating the submodules blorgit should once again be working.
If I had the time I'd love to re-write this in Clojure so that a single
jar file could be downloaded and run directly without having to worry
about installing the entire ruby stack locally.
Best -- Eric
Michaël Parienti <michael@parienti.name> writes:
> Hi,
>
> On Thu, 14 Oct 2010 16:52:05 -0600
> "Eric Schulte" <schulte.eric@gmail.com> wrote:
>
>> If not, then run
>>
>> git submodule init
>> git submodule update
>>
>> in the base of the blorgit repo, and give it another try.
>
> I got exactly the same error message as Ezequiel Birman, and I did
> install the submodule with these commands.
>
>
>> This could also be caused by changes to ruby since blorgit was last
>> updated, in which case I may be able to take a look and see if I can
>> fix it, but it's been almost a year since I've done any ruby
>> programming, so this make not happen quickly...
>
> I hope it will be easy to fix, because blorgit is really useful. I use
> org-mode for several years, coupled with git. Now I need to share the
> editing of some pages. A web interface is the more convenient way to do
> it.
>
> Regards
next prev parent reply other threads:[~2010-10-17 18:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 14:14 blorgit build Ezequiel Birman
2010-10-14 22:52 ` Eric Schulte
2010-10-17 13:40 ` Michaël Parienti
2010-10-17 18:48 ` Eric Schulte [this message]
2010-10-17 20:01 ` Michaël Parienti
2010-10-26 22:00 ` Ezequiel Birman
2010-10-28 15:05 ` Eric Schulte
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sk047j0w.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=michael@parienti.name \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).