Monthly gem5 Developers' Meeting - June 11th at 4pm (UTC)

[Harshil2107]

The monthly gem5 Developers' Meeting will take place on June 11th at 4pm UTC.

If you would like to add anything to the agenda please create a comment below.

Agenda:

• Discussion about clang format: @BobbyRBruce
• misc,util-m5,ext-testlib: add color to panics/warnings/infos #3204 : Large UI change, general discussion if it is ok to merge

Metting Information:

Microsoft Teams meeting

Join:
https://teams.microsoft.com/meet/278513025321362?p=MBXqODgjnVUxWh7uZs

Meeting ID:
278 513 025 321 362

Passcode:
eH3xp7ha

[powerjg]

Here's a recipe for how to fix it when you get a clang format error in CI.

#2861 (comment)

1. Make sure clang format is up to date:

pip install clang-format==18.1.8

2. Set up an interactive rebase

git rebase -i develop

and set all commits to edit. Then,

3. Undo the current commit (keeping all changes in the working tree):

   git reset HEAD~1

4. Stage only the files that were part of the original commit:

   git diff --name-only HEAD ORIG_HEAD | xargs git add

   (This dynamically gets the list of files changed between the parent commit HEAD and the original commit ORIG_HEAD, and stages only those files).

5. Re-commit the changes (triggering the hooks):

   git commit -c ORIG_HEAD

6. Handle pre-commit hook modifications (if any):
   If the clang-format hook automatically formats files, stage those formatting updates and commit:

   git add -u
   git commit -c ORIG_HEAD

7. Continue the rebase:

   git rebase --continue

[powerjg]

@Harshil2107 can you add this to the agenda:

#3204

Discussion of this PR. This is a relatively large UI change to gem5. I don't see anything wrong or bad about this change, but before making a big UI change I would like to make sure there are no objections from the community.