# Agenda for XALT Zoom Mtg Oct. 27 at 10:00 US Central (15:00 UTC)

- Q & A
- New Release of XALT 2.10.44
- Issue about Python package tracking (from Lisa)
- Adding Try block around importing config.py file
- this allows for better error reporting in case of mistakes in the config file
- "`master`" branch renamed to "`main`" in XALT GitHub repo
- A possible discussion of git worktrees
- see notes below
- Presentation on Link Record Generation in XALT
- slides available at https://github.com/xalt/xalt/blob/main/my_docs/22/xalt_monthly_mtg_2022_10_27/presentation.pdf
- syslogv1 tranmission style is only still supported for legacy reasons
- required making changes to syslog configuration
- syslogv1 tries to log everything in a single message (not in blocks), which causes trouble when ingesting event records again
- curl is used by CSCS to inject data into their ELK setup

- next meeting is 15 Dec 2022 at 10:00 CST (15:00 UTC)
- no XALT meeting in Nov'22 due to SC22 + Thanksgiving

- Robert will be attending SC'22 in case anyone wants to meet up!

### Attendees

- Robert McLay (TACC)
- Amit Ruhela (TACC)
- Kenneth Hoste (HPC-UGent)
- Lisa Childers (Argonne National Lab)
- Ben Fulton (Indiana University)
- Justin Cook (NERSC)

### Demo on git worktree

- see https://git-scm.com/docs/git-worktree
- Why use git worktree commands when branching:
- A replacement for **git stash** and **git stash pop**
- Or **git clone** and check out a different branch somewhere in your account
- git worktree is much faster than git clone (and branches do not get lost in your account)
- Branches can be left in an incomplete state. You can come back to them later
- Important commands
- git worktree add **directory** -> create or open a branch
- git worktree add ../testing -> switch or open **testing** branch
- git worktree list -> list checked out branches
- git worktree remove **directory** -> remove branch and files
- Doesn't work with git submodules
- Uses hard paths: do not rename directory layout
- alias gw="git worktree"
- Example of three different directory layouts
- Have worktrees at the same level as bare repo (type A)
- Have layout like ~/w/lmod/{bare,master,testing} (type B)
- Checkout main branch then place worktrees in ~/w/lmod/.worktree (type C)
- cd w/lmod; git worktree add .worktree/testing
- (Add .worktrees in .gitignore)
- Youtube links
- (type A) https://www.youtube.com/watch?v=2uEqYw-N8uE
- (type C) https://www.youtube.com/watch?v=4_p1OdLeDLE&t
- (Using worktrees to manage dotfiles w/o symlinks) https://www.youtube.com/watch?v=tBoLDpTWVOM
- when using "git worktree", there's only one copy of the Git metadata (normally the .git folder. In this case its the bare directory)
- big difference if you have lots of branches checked out via worktrees (vs totally separate clones of the repo)
- for TACC/Lmod repo: ~24MB of Git metadata, 44MB of repo contents