From: Eric Wong <e@80x24.org>
To: Pirate Praveen <praveen@debian.org>
Cc: unicorn-public@bogomips.org
Subject: Re: Request to follow SemVer/mention it in homepage
Date: Wed, 30 Sep 2015 19:51:42 +0000 [thread overview]
Message-ID: <20150930195142.GA23228@dcvr.yhbt.net> (raw)
In-Reply-To: <560C07FD.9060208@debian.org>
Pirate Praveen <praveen@debian.org> wrote:
> Can you mention the recommended way of adding unicorn in a Gemfile in
> your home page?
I'm not very knowledgeable about bundler, but app servers probably
should not be in any packaged Gemfile at all.
> gitlab and diaspora has unicorn in their Gemfile, for a user they want
> gitlab or diaspora and they don't care if its using unicorn or puma or
> passenger.
>
> I need some kind of an official statement about compatibility which I
> can show to projects like gitlab and diaspora, so they don't insist on
> exact patch release of unicorn. I could patch the Gemfile, but that
> adds extra burden on me as a maintainer which I'd like to avoid if
> possible.
"Official statements" do not have much weight behind them; history does.
They can look at the git history (especially that of manpages and
documentation) to see the only feature removals were for undocumented
cruft.
Personally, I intensely dislike "official" things; so people shouldn't
take what I (or anybody) writes as gospel.
next prev parent reply other threads:[~2015-09-30 19:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 6:38 Request to follow SemVer/mention it in homepage Pirate Praveen
2015-09-29 7:36 ` Eric Wong
2015-09-29 7:46 ` Lin Jen-Shin (godfat)
2015-09-29 8:00 ` Pirate Praveen
2015-09-29 19:36 ` Eric Wong
2015-09-30 16:04 ` Pirate Praveen
2015-09-30 19:51 ` Eric Wong [this message]
2015-10-01 4:56 ` Pirate Praveen
2015-10-01 11:18 ` Pirate Praveen
2015-10-01 19:06 ` Eric Wong
2015-09-29 9:26 ` Jérémy Lecour
2015-09-29 19:43 ` Eric Wong
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://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150930195142.GA23228@dcvr.yhbt.net \
--to=e@80x24.org \
--cc=praveen@debian.org \
--cc=unicorn-public@bogomips.org \
/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://yhbt.net/unicorn.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).