From: uzibalqa <uzibalqa@proton.me>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Source code, git and cvs
Date: Thu, 20 Jul 2023 19:12:21 +0000 [thread overview]
Message-ID: <QN7MvquGpYSIhVjnXYjtmGwzONULJHx6kUoRJz4Ty1tni8WprB7Dtivblvkn26QHvHLAa9iwOu3dc6cb5AfmKIrUHmFAs6hWINNl_gy_O7I=@proton.me> (raw)
In-Reply-To: <83zg3q1ll9.fsf@gnu.org>
------- Original Message -------
On Friday, July 21st, 2023 at 6:31 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Thu, 20 Jul 2023 17:33:41 +0000
> > From: uzibalqa uzibalqa@proton.me
> > Cc: help-gnu-emacs@gnu.org
> >
> > > > README should describe both immediately at the start. Not just about
> > > > installing from the tarball.
> > >
> > > We clearly disagree.
> >
> > Of course, hide it and make things more difficult for new users. And then
> > expect them to figure out things by themselves. And when they ask questions,
> > never be straightforward and give them the code they need to use. It is their
> > job to go through the ever increasing obfuscation of information embedded within
> > deeper and deeper levels of cyclomatic complexity. Classic example of development
> > malpractice.
>
>
> You should stop your arrogant and rude remarks about project practices
> that you just learned yesterday. It is not wise, to say the least, to
> show your ignorance by claiming you are right even after you have been
> pointed to your mistakes and stuff you missed in the docs.
Yes, I am right, you are wrong.
> The README, INSTALL, etc. files in the top-level directory are the
> result of many years of experience and many users contributing to
> them, they are not just random text that was written yesterday and
> therefore needs to be polished. It's already polished, so any change
> you suggest based on 5 sec of thought is more than likely to have
> downsides that were already considered and rejected in the long
> history of Emacs development.
Typical nonsense.
> You have ample opportunity to exercise some humility and learn (and
> you have a lot to learn, believe me) before you get to the position
> where you might "know better", and have the moral right to teach us
> what is "malpractice". Suggest to use that opportunity.
I just look at things how they are, so one can effortlessly navigate
through the material. There is no need to be humble and I definitely
have the autonomy to take action without approval or authority. I am
certainly not bound by any requirement of external validation or permission
to do so.
next prev parent reply other threads:[~2023-07-20 19:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 12:01 Source code, git and cvs uzibalqa
2023-07-20 13:38 ` Po Lu
2023-07-20 13:58 ` uzibalqa
2023-07-20 14:23 ` Eli Zaretskii
2023-07-20 15:09 ` uzibalqa
2023-07-20 15:34 ` Robert Pluim
2023-07-20 15:36 ` Eli Zaretskii
2023-07-20 15:47 ` uzibalqa
2023-07-20 16:35 ` Eli Zaretskii
2023-07-20 17:33 ` uzibalqa
2023-07-20 18:31 ` Eli Zaretskii
2023-07-20 19:12 ` uzibalqa [this message]
2023-07-20 20:10 ` uzibalqa
2023-07-21 5:22 ` Eli Zaretskii
2023-07-21 6:12 ` Po Lu
2023-07-21 10:43 ` uzibalqa
2023-07-21 10:59 ` uzibalqa
2023-07-21 11:18 ` uzibalqa
2023-07-21 12:30 ` Eli Zaretskii
2023-07-21 12:40 ` uzibalqa
2023-07-21 12:51 ` Eli Zaretskii
2023-07-21 4:27 ` tomas
2023-07-21 10:35 ` uzibalqa
2023-07-21 12:12 ` Po Lu
2023-07-21 12:52 ` uzibalqa
2023-07-21 14:20 ` [External] : " Drew Adams
2023-07-21 15:30 ` uzibalqa
2023-07-20 16:05 ` uzibalqa
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='QN7MvquGpYSIhVjnXYjtmGwzONULJHx6kUoRJz4Ty1tni8WprB7Dtivblvkn26QHvHLAa9iwOu3dc6cb5AfmKIrUHmFAs6hWINNl_gy_O7I=@proton.me' \
--to=uzibalqa@proton.me \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.