Re: Choice of bug tracker

[Visuwesh]

[வெள்ளி செப்டம்பர் 01, 2023] Dmitry Gutov wrote:

>> I did not have problems with sending the mail to the right address but
>> knowing whether my mail reached the mailing list/debbugs was an issue
>> since I could not see it pop up in the bug-gnu-emacs mailing list
>> archive.  Much later I learnt that there is a manual approval process
>> for fresh email addresses and that's why my acknowledgement mail was
>> sent some 10 hours later (I went to sleep after submitting said bug
>> report).  If there was a message along the lines of, “Your message has
>> been received and will be forwarded to the Emacs developers once your
>> email address has been manually approved to check whether your mail is
>> spam or not” I think the first experience would have been smoother.
>> As for submitting patches, I much much much much prefer the Emacs
>> way™.
>> It is so much better than forking the repo, creating a new branch,
>> fighting with Git to merge/rebase and push properly without --force (I
>> still don't know how to do the latter FWIW). And don't get me started on
>> amendments after creating the PR...  For Emacs, I can develop the patch
>> however I want and simply attach it to a mail---I cannot emphasise how
>> much simpler and effortless this feels.  It is a good thing that Emacs
>> actually prefers patches as assignment over `git send-email'---nothing
>> is more of a pain than setting up an email client especially in a
>> CLI/TUI setting.  When you have only used the GMail/Yahoo web client for
>> email, all the terminologies that the man page and the tutorials throw
>> at you simply flies over your head and you give up.  Now, the most
>> common mail provider Gmail has made it a huge PITA to use a custom email
>> client as well...
>> So let me reiterate: I find it so comforting that Emacs accepts
>> patches
>> (1) via email, and (2) as attachments.
>
> I'm glad that you like it here, and we should say that the ability to
> submit patch via an attachment shouldn't ever go away. I even post
> patches on Github inline (via markdown blocks) sometimes, puzzling
> occasional passers-by. So the number of options how to submit and
> discuss a patch shouldn't go down in any case, only up.
>
> Note, however, that knowing how to work with Git and understanding its
> repository model (and knowing to to do merges/rebases/etc) is going to
> be very useful for your career, at least if you're a programmer or a
> data scientist.

I can merge and rebase fine now but I can never get `git push' to work
to my fork repo.  Whenever I lookup how to `git push' without --force, I
could never use the answers given in the internet.

>>> There should also be SourceHut on this scale, but I don't know where
>>> to put it.
>> Cannot comment on how everyone else uses Sourcehut but my experience
>> was
>> slightly better than Debbugs because I got instant feedback from the
>> mailing list archive and Philip accepts patches as attachments.  ;-)
>> Generally, I don't find their web UI all that useful since they drop the
>> entire message after the attachment.  I am not sure if there are plans
>> to fix it since Sourcehut people prefer `git send-email' AFAIK.
>
> Yes, they do have a weak spot in the web UI department. But basically
> anything is better than Debbugs, IMO ;-(

At least for search, yhetil.org is much better (read: actually working).