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