unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, bruce.connor.am@gmail.com,
	Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: bug#20968: 25.0.50; Be able to specify the output directory for `byte-compile-file'
Date: Sun, 05 Jul 2015 12:27:48 -0400	[thread overview]
Message-ID: <jwvtwtik29t.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <83mvzaws3s.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 05 Jul 2015 18:18:15 +0300")

[ Please take out the 20968@... from the Ccs.  ]

> That's not the use case I was talking about.  Looking up questions
> already asked means using a search engine, which will find the answers
> wherever they are, be it on gnu.emacs.help of stack-overflow.

No, the curating (tagging, voting, and editing) makes a significant
difference: you don't need to read N different messages (hopefully
connected via threading) to get the overall picture.

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.  Sometimes I can get more details and info in the
developer's mailing list archive, but it takes more effort and technical
expertise to find it and digest it.

> I was talking about someone who wants to ask a question never
> asked/answered before.

In that case it mostly depends on who's available to answer
the question.  I think in this respect the average proficiency level on
emacs.stackexchange is very much comparable to that of gnu.emacs.help.

As for redirecting people to *us* (i.e. emacs-devel or debbugs), I find
it neither harder nor easier on stack-foo than on gnu.emacs.help.


        Stefan



       reply	other threads:[~2015-07-05 16:27 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                       ` Stefan Monnier [this message]
2015-07-05 16:31                         ` bug#20968: 25.0.50; Be able to specify the output directory for `byte-compile-file' 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

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=jwvtwtik29t.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=bruce.connor.am@gmail.com \
    --cc=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.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://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).