[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130602210126.GA14687@openwall.com>
Date: Mon, 3 Jun 2013 01:01:26 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: john-users vs. john-dev (was: OS X Macbook problems trying to use GPU)
On Sun, Jun 02, 2013 at 12:00:06PM -0700, Martin wrote:
> Sorry if I'm misusing this list, but this started as a question about my computer hanging when I tried to use the -opencl formats after making the 'macosx-x86-64-opencl' build.
Yes, and that question was more appropriate for john-users rather than
for john-dev, unless you included a source code patch (thereby directly
contributing to JtR development). Just because you're reporting what
may be a bug does not mean that the message is for -dev rather than -users.
> Now I have tried other formats and I have some results. Should I post that in the users forum? This seems like a code issue, but I will move this thread there
Yes, 100% of what you post so far belongs on john-users and not john-dev.
Just because something is likely a "code issue" does not mean it is a
john-dev topic, unless you're directly involved in working on the code
(e.g., include a source code patch right in your message).
> if you think this is something that users will be able to help me resolve.
While john-users is a list for the users, that does not mean that only
users are subscribed and replying. All of the most active JtR
developers are also on john-users, and we try to ensure that all
questions receive an answer. It is better for us to answer those
questions on john-users rather than on john-dev because that way our
answers benefit many other users at once, because in some cases there
are helpful answers from other users, and because it helps us keep the
traffic on john-dev more focused on actual development.
Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
