Void Linux discussion
 help / color / mirror / Atom feed
From: Juan RP <xtr...@gmail.com>
To: voidlinux@googlegroups.com
Cc: boug...@rubyists.com
Subject: Re: Void-Stable?
Date: Tue, 7 Apr 2015 21:53:45 -0700 (PDT)	[thread overview]
Message-ID: <3ca4287e-1d53-423c-b149-eb397bde3f17@googlegroups.com> (raw)
In-Reply-To: <87mw2kqq99.fsf@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 144 bytes --]


I agree with Christian :-)

But I waste enough time daily to even think on a periodic stable release, 
of course
help is always welcome.

[-- Attachment #1.2: Type: text/html, Size: 173 bytes --]

      reply	other threads:[~2015-04-08  4:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-06 23:16 Void-Stable? bougyman
2015-04-06 23:33 ` Void-Stable? bougyman
2015-04-07  0:34 ` Void-Stable? Kevin Berry
2015-04-07  8:34 ` Void-Stable? Stefan Mühlinghaus
2015-04-07  8:47 ` Void-Stable? Christian Neukirchen
2015-04-08  4:53   ` Juan RP [this message]

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=3ca4287e-1d53-423c-b149-eb397bde3f17@googlegroups.com \
    --to="xtr..."@gmail.com \
    --cc="boug..."@rubyists.com \
    --cc=voidlinux@googlegroups.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).