2025/freebsd-hackers/20250203.freebsd-hackers
Messages: 44, sorted by subject
|
Last update: Mon Feb 3 0:07:06 2025
|
|
home | up | archive sorted by: subject | author | date | reverse date
1. Feb 1 Bjoern A. Zeeb %b with uint64_t? 2. Feb 1 Konstantin Belousov Re: %b with uint64_t? 3. Feb 1 Sulev-Madis Silber =?US-ASCII?Q?Re=3A_Provisions_to_the_contribution_gu?= =?US-ASCII?Q?idelines_for_using_LLM_generated_code?= 4. Jan 30 Sulev-Madis Silber =?US-ASCII?Q?Re=3A_Provisions_to_the_contribution_gu?= =?US-ASCII?Q?idelines_for_using_LLM_generated_code?= 5. Jan 31 Sulev-Madis Silber =?US-ASCII?Q?Re=3A_Provisions_to_the_contribution_gu?= =?US-ASCII?Q?idelines_for_using_LLM_generated_code?= 6. Feb 2 Steve Kargl bhyve an missing packages? 7. Feb 2 Miroslav Lachman Re: bhyve an missing packages? 8. Feb 2 =?UTF-8?Q?Olivier_Cochard= Re: bhyve an missing packages? 9. Feb 2 =?UTF-8?Q?Olivier_Cochard= Re: bhyve an missing packages? 10. Feb 2 Steve Kargl Re: bhyve an missing packages? 11. Feb 2 Miroslav Lachman Re: bhyve an missing packages? 12. Jan 27 Konstantin Belousov Re: gcc14 static linking ends with segfault 13. Jan 27 Steve Kargl Re: gcc14 static linking ends with segfault 14. Jan 27 Dimitry Andric Re: gcc14 static linking ends with segfault 15. Jan 27 Steve Kargl Re: gcc14 static linking ends with segfault 16. Jan 27 Steve Kargl Re: gcc14 static linking ends with segfault 17. Jan 27 Dimitry Andric Re: gcc14 static linking ends with segfault 18. Jan 27 Konstantin Belousov Re: gcc14 static linking ends with segfault 19. Jan 27 Steve Kargl Re: gcc14 static linking ends with segfault 20. Jan 27 Dimitry Andric Re: gcc14 static linking ends with segfault
21. Jan 27 Konstantin Belousov Re: gcc14 static linking ends with segfault 22. Jan 28 Manas Ghandat Re: GSoC project Ideas 23. Jan 28 Manas Ghandat Re: GSoC project Ideas 24. Jan 28 Lorenzo Salvadore Re: GSoC project Ideas 25. Jan 28 Lorenzo Salvadore Re: GSoC project Ideas 26. Jan 30 paige@paige.bio Provisions to the contribution guidelines for using LLM generated code 27. Jan 30 =?UTF-8?B?0K/RgNC+0YHQu9Cw Re: Provisions to the contribution guidelines for using LLM generated code 28. Jan 30 David Chisnall Re: Provisions to the contribution guidelines for using LLM generated code 29. Jan 31 paige@paige.bio Re: Provisions to the contribution guidelines for using LLM generated code 30. Jan 31 David Chisnall Re: Provisions to the contribution guidelines for using LLM generated code 31. Jan 31 David Chisnall Re: Provisions to the contribution guidelines for using LLM generated code 32. Jan 31 paige@paige.bio Re: Provisions to the contribution guidelines for using LLM generated code 33. Jan 31 paige@paige.bio Re: Provisions to the contribution guidelines for using LLM generated code 34. Jan 31 Alexander Leidinger Re: Provisions to the contribution guidelines for using LLM generated code 35. Jan 28 Tomek CEDRO Re: Suggestions for Ryzen 9 motherboards 36. Jan 28 Daniel Engberg Re: Suggestions for Ryzen 9 motherboards 37. Jan 28 Tomek CEDRO Re: Suggestions for Ryzen 9 motherboards 38. Jan 28 Mohammad Noureldin Re: Suggestions for Ryzen 9 motherboards 39. Jan 28 Paul Floyd Re: Suggestions for Ryzen 9 motherboards 40. Jan 28 Paul Floyd Re: Suggestions for Ryzen 9 motherboards
41. Feb 2 Mohammad Noureldin Re: Thunderbolt3/USB4 targeting: should the wiki materials be more explicit about Thunderbolt 3 vs. Thunderbolt 4 distinctions? 42. Feb 2 Mark Millard Re: Thunderbolt3/USB4 targeting: should the wiki materials be more explicit about Thunderbolt 3 vs. Thunderbolt 4 distinctions? 43. Jan 30 Mohammad Noureldin Re: Thunderbolt3/USB4 targeting: should the wiki materials be more explicit about Thunderbolt 3 vs. Thunderbolt 4 distinctions? 44. Jan 30 Mark Millard Re: Thunderbolt3/USB4 targeting: should the wiki materials be more explicit about Thunderbolt 3 vs. Thunderbolt 4 distinctions?
home | up | archive sorted by: subject | author | date | reverse date