git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Why Is There No Bug Tracker And Why Are Patches Sent Instead Of Pull Requests

From
Andrew Ardill <andrew.ardill@gmail.com>
Date
Mar 1, 2012, 01:20 UTC
Message-ID
<CAH5451krbyZCRm8JR+kf+8cDqkbnQKnzXGxmncmRF9YPXvckNA@mail.gmail.com>
In-Reply-To
<7vaa41qgf4.fsf@alter.siamese.dyndns.org>
On 1 March 2012 12:05, Junio C Hamano <gitster@pobox.com> wrote:
Show 12 quoted lines
> Andrew Ardill <andrew.ardill@gmail.com> writes:
>
>> On 1 March 2012 11:37, Greg Troxel <gdt@ir.bbn.com> wrote:
>>>
>>> Do people really think it's reasonable to use non-Free tools to develop
>>> git? That seems surprising to me.
>>
>> Maybe not, and if that is the case I am more than happy to let this die.
>
> I won't speculate how big or small part of the Git community you would be
> repelling by using a closed/commertial offering. It may not be such a big
> deal, or it may be. I simply do not know.
Neither do I - let's find out!
> But we will never find out until we try. The same thing can be said for
> the usefulness of having a bug tracker and feasibility of keeping it
> reasonably clean and useful over time with volunteer effort.  I commend
> you for finally stepping up and biting the bullet to start an experiment.

I have been meaning to get this going for a few months now, the latest thread kickstarted me again.

Show 7 quoted lines
> One request I may have is to give read/browse-only access to unregistered
> users without any account (I hate having to maintain credentials to random
> websites, and I imagine so do many other people), but I am not the target
> audience, so please do not bend backwards to implement such if it is too
> much trouble with the system.
>
> Thanks.

I have given browse access by default to Anyone (does not require log-in). JIRA is highly customisable, so most requests are typically feasible.

Regards,
Andrew Ardill
Previous: Junio C HamanoNext: Miles Bader
Message 11 of 37 in “Why Is There No Bug Tracker And Why Are Patches Sent Instead Of Pull Requests”
  1. opticyclicFeb 29, 2012
  2. Brian GernhardtFeb 29, 2012
  3. Junio C HamanoFeb 29, 2012
  4. Jonathan NiederFeb 29, 2012
  5. Andrew ArdillFeb 29, 2012
  6. Greg TroxelMar 1, 2012
  7. Andrew ArdillMar 1, 2012
  8. Junio C HamanoMar 1, 2012
  9. Andrew ArdillMar 1, 2012
  10. Junio C HamanoMar 1, 2012
  11. Andrew ArdillMar 1, 2012
  12. Miles BaderMar 1, 2012
  13. Andrew ArdillMar 1, 2012
  14. Scott ChaconMar 1, 2012
  15. Junio C HamanoMar 1, 2012
  16. Thomas RastMar 1, 2012
  17. Ævar Arnfjörð BjarmasonMar 1, 2012
  18. Andrew ArdillMar 1, 2012
  19. Andrew ArdillMar 1, 2012
  20. Junio C HamanoMar 1, 2012
  21. Neal KreitzingerMar 2, 2012
  22. Jonathan NiederMar 2, 2012
  23. Junio C HamanoMar 2, 2012
  24. Neal KreitzingerMar 2, 2012
  25. Jonathan NiederMar 2, 2012
  26. Junio C HamanoMar 2, 2012
  27. Andreas EricssonMar 2, 2012
  28. Junio C HamanoMar 2, 2012
  29. Andrew ArdillMar 7, 2012
  30. Vincent van RavesteijnMar 7, 2012
  31. Joern HuxhornMar 7, 2012
  32. Jonathan NiederMar 7, 2012
  33. Joern HuxhornMar 7, 2012
  34. Pau Garcia i QuilesMar 7, 2012
  35. Phil HordMar 7, 2012
  36. Carlos Martín NietoFeb 29, 2012
  37. Sitaram ChamartyFeb 29, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.