edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] wordexp again
Date: Sat, 18 Apr 2015 12:33:48 -0700	[thread overview]
Message-ID: <87wq195izn.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20150418130910.GM5949@toaster.adamthompson.me.uk> (Adam Thompson's message of "Sat, 18 Apr 2015 14:09:10 +0100")

Adam Thompson <arthompson1990@gmail.com> writes:

> users really shouldn't be pulling the latest git and expecting everything to be
> fully working, that's not what version control's for in a collaberative project.

Yes.  Basically, if you're going to run from git, you need to follow
this list.  Also note if you have an NNTP client, you can even follow
it without subscribing.  Just point at news.gmane.org and read the
gmane.comp.web.edbrowse.devel newsgroup.  I should probably add a note
about that to the website and README.  There are lots of people out
there who prefer to remain anonymous, and they'd benefit from that interface.

> but I'd personally change the github page to point to this list rather than the
> commandline list since git is our development environment.

Yes, but the folks Karl is discussing are contacting him directly.
I follow both lists, and the other has been silent for a while.

> That being said, I accept that the build process is rather involved at the
> minute, so we may need to work to automate some of that.

The only thing that is fiddly is the binary build process.
Releasing the code is easy.

Your message has reminded me of another problem, though.
Right now, the edbrowse web site is hosted on my server.  If it needs to
change, for whatever reason, I'm the only one who can change it.
Currently, I haven't come up with a fix that makes me completely happy,
but I'll keep thinking on it.
You guys may end up with some kind of (restricted) ssh access to the
machine hosting the site.  I could also set up a page on github, say
edbrowse.github.com, and we could all push to that.  But github doesn't
make it easy to host binary content like tarballs and executables, I think.

-- Chris

  reply	other threads:[~2015-04-18 19:34 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 21:40 Karl Dahlke
2015-04-17  7:12 ` Adam Thompson
2015-04-17 12:50   ` Adam Thompson
2015-04-17 13:33     ` Karl Dahlke
2015-04-17 17:59       ` Adam Thompson
2015-04-17 13:47     ` Karl Dahlke
2015-04-17 18:01     ` Karl Dahlke
2015-04-17 21:34       ` Adam Thompson
2015-04-17 21:58         ` Adam Thompson
2015-04-17 22:25           ` Karl Dahlke
2015-04-17 22:43             ` Adam Thompson
2015-04-17 23:14               ` Karl Dahlke
2015-04-17 22:28           ` Adam Thompson
2015-04-17 22:39             ` Karl Dahlke
2015-04-18 10:53               ` Adam Thompson
2015-04-18  4:18     ` Karl Dahlke
2015-04-18 10:49       ` Adam Thompson
2015-04-18 11:34         ` Karl Dahlke
2015-04-18 13:09           ` Adam Thompson
2015-04-18 19:33             ` Chris Brannon [this message]
2015-04-18 20:05               ` Adam Thompson
2015-04-18 23:03                 ` Chris Brannon
2015-04-18 12:36         ` Karl Dahlke
2015-04-18 12:54           ` Adam Thompson
2015-04-18 13:09             ` Karl Dahlke
2015-04-18 13:24               ` Adam Thompson
2015-04-18 13:45                 ` Karl Dahlke
2015-04-18 17:44                   ` Adam Thompson
2015-04-18 19:48                     ` Karl Dahlke
  -- strict thread matches above, loose matches on Subject: below --
2015-01-09 22:44 Karl Dahlke
2015-01-09 22:19 Karl Dahlke
2015-01-09 22:29 ` Chris Brannon
2015-01-09 21:16 Chris Brannon

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=87wq195izn.fsf@mushroom.localdomain \
    --to=chris@the-brannons.com \
    --cc=Edbrowse-dev@lists.the-brannons.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).