unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: bug#20968: 25.0.50; Be able to specify the output directory for `byte-compile-file'
Date: Sun, 5 Jul 2015 20:44:49 +0100	[thread overview]
Message-ID: <CAAdUY-J9mhyZM7A7iHkZYBNhC45YJBe2=0bGwODcY-gQKLofFg@mail.gmail.com> (raw)
In-Reply-To: <83io9ywop0.fsf@gnu.org>

>> When I search (via, say, DuckDuckGo) for answers to a particular
>> problem, I generally find that the answers I find in stackoverflow are
>> generally more directly usable and of higher quality than what I may
>> find elsewhere.
>
> Then we may wish to make our answers better and more usable as well.
> Again, if we want to; it doesn't sound to me people are too
> enthusiastic about this.

Yes, I find it a bit hard to be enthusiastic about it. There's nothing
wrong with trying to make help-gnu-emacs better, but as long as it's a
mailing list it's going to have a very hard time being highly ranked
in search engines.

Besids, to have other sites dedicated to Emacs is only a sign of a
healthy (and dedicated) community. If we're worried that that
information might go away without notice, we could archive it
ourselves (that's pretty trivial, even).



      parent reply	other threads:[~2015-07-05 19:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <23829743-922e-4304-8ab3-b762b8193860@default>
     [not found] ` <74y4iytdjg.fsf@fencepost.gnu.org>
     [not found]   ` <e68f1dc9-9e8f-4f54-af8f-a5bb23160576@default>
     [not found]     ` <83pp49zb03.fsf@gnu.org>
     [not found]       ` <jwv8uaxp9k3.fsf-monnier+emacsbugs@gnu.org>
     [not found]         ` <83egkpyvvd.fsf@gnu.org>
     [not found]           ` <CAAdUY-+_4DzOCe6Yp19PWkxH+Ba3FGm4mCbeafho+8KodyKanQ@mail.gmail.com>
     [not found]             ` <83si94xrcn.fsf@gnu.org>
     [not found]               ` <55991ADF.8070208@yandex.ru>
     [not found]                 ` <83pp46wu2z.fsf@gnu.org>
     [not found]                   ` <5599450F.4050609@yandex.ru>
     [not found]                     ` <83mvzaws3s.fsf@gnu.org>
2015-07-05 16:27                       ` bug#20968: 25.0.50; Be able to specify the output directory for `byte-compile-file' Stefan Monnier
2015-07-05 16:31                         ` Eli Zaretskii
2015-07-05 18:09                           ` Stefan Monnier
2015-07-05 19:30                             ` Artur Malabarba
2015-07-05 18:11                           ` Stefan Monnier
2015-07-05 19:18                             ` Artur Malabarba
2015-07-05 19:44                           ` Artur Malabarba [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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAAdUY-J9mhyZM7A7iHkZYBNhC45YJBe2=0bGwODcY-gQKLofFg@mail.gmail.com' \
    --to=bruce.connor.am@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.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).