User Information

Username sebasjm

Timeline

   2025-04-16 .. 2025-04-23   
Prev Next
sebasjm commented on issue 0009767
2025-04-22 22:01
sebasjm resolved issue 0009767
2025-04-22 22:01
sebasjm commented on issue 0009767
2025-04-22 22:00
sebasjm unassigned issue 0009770
2025-04-22 19:27
sebasjm commented on issue 0009487
2025-04-22 17:20
sebasjm resolved issue 0009487
2025-04-22 17:20
sebasjm assigned issue 0009770 to Christian Grothoff
2025-04-22 16:13
sebasjm created issue 0009770
2025-04-22 16:13
sebasjm commented on issue 0009768
2025-04-21 21:23
sebasjm picked up issue 0009768
2025-04-21 20:30
sebasjm created issue 0009768
2025-04-21 20:30
sebasjm commented on issue 0009695
2025-04-21 17:39
sebasjm commented on issue 0009695
2025-04-21 16:18
sebasjm assigned issue 0009661 to Florian Dold
2025-04-21 12:48
sebasjm commented on issue 0009661
2025-04-21 12:48
sebasjm commented on issue 0009757
2025-04-21 12:42
sebasjm resolved issue 0009757
2025-04-21 12:42
sebasjm assigned issue 0009752 to Christian Grothoff
2025-04-17 18:04
sebasjm created issue 0009752
2025-04-17 18:04
sebasjm resolved issue 0009751
2025-04-17 16:04
sebasjm commented on issue 0009751
2025-04-17 16:03
sebasjm assigned issue 0009751 to Christian Grothoff
2025-04-17 15:44
sebasjm created issue 0009751
2025-04-17 15:44
sebasjm resolved issue 0009585
2025-04-17 03:25
sebasjm commented on issue 0009349
2025-04-17 02:17
sebasjm assigned issue 0009349 to Christian Grothoff
2025-04-17 01:45
sebasjm attached file crash_challenger.sh to issue 0009349
2025-04-17 01:45
sebasjm attached file removes_read_only.sh to issue 0009349
2025-04-17 01:45
sebasjm commented on issue 0009349
2025-04-17 01:45
sebasjm resolved issue 0009725
2025-04-17 01:13
sebasjm commented on issue 0009725
2025-04-17 01:13
sebasjm resolved issue 0009737
2025-04-17 01:07