l_samenv fad330b71d fixed README
added a plan, how to keep mlz and local git in sync
2021-02-26 17:02:26 +01:00
2021-02-26 15:29:44 +01:00
2020-09-10 15:47:04 +02:00
2019-09-26 16:24:58 +02:00
2020-04-09 17:04:32 +02:00
2020-04-09 17:04:09 +02:00
2021-02-26 15:29:44 +01:00
2020-01-15 08:15:35 +01:00
2020-05-04 16:30:16 +02:00
2021-02-26 17:02:26 +01:00
2020-04-09 17:04:09 +02:00

Frappy Framework

current running code at SINQ, with newest changes not yet pushed through the Gerrit workflow at MLZ

branches:

  • mlz: master from forge.frm2.tum.de:29418/sine2020/secop/playground
  • master: keep in sync with above before pushing to psi repo (git.psi.ch:sinqdev/frappy.git)
  • work: current working version, usually in use on /home/l_samenv/frappy (and on neutron instruments) this should be a copy of an earlier state of the wip branch
  • wip: current test version, usually in use on /home/l_samenv/frappy_wip
  • lastsynced: the last synced state between mlz and wip

lastsynced | | | | master work | | wip

apply commits from master to work: (rebase ?) or use cherry-pick:

git cherry-pick ..

where sha1 is the last commit already in wip, and sha2 ist the last commit to be applied for a single commit .. may be omitted

the wip branch is also present in an other directory (currently zolliker/switchdrive/gitmlz/frappy), where commits may be cherry picked for input to Gerrit. As generally in the review process some additonal changes are done, eventually a sync step should happen:

  1. make copies of branches work and wip
  2. pull changes to master from mlz
  3. cherry-pick commits (from master) to lastsynced
  4. copy lastsynced branch to wip with 'git checkout -B wip'
  5. in wip cherry-pick commits not yet feeded into Gerrit from above wip copy
  6. decide from where to take new work branch (probably from wip)
  7. delete branch copies not needed any more
Description
PSI local frappy repo, probably ahead of git/gerrit at MLZ
Readme 4.6 MiB
Languages
Python 99.9%