On 29/08/2025 00:20, gregor herrmann wrote:
On Thu, 28 Aug 2025 15:04:42 -0700, Otto Kekäläinen wrote:
>Also dep12-migrate performs the actual migration, while
>dep-14-convert-git-branch-names.sh only suggests what should be done.
Running dep-14-convert-git-branch-names will print a list of commands
to run, which you easily can just copy-paste to run.
4000 times? Manually? Seriously?
i think: yes
if you are managing 4000 packages, then I assume that these packages are
all setup the same (e.g. according to your team policy).
in this case, i would just run dep-14-convert-git-branch-names once to
get the commands to run, test them and then paste them into a
script-file (possibly adding some debugging output, just in case
something does go wrong); finally execute the magic:
```
for d in */; do
echo "=============== $d ============"
cd "${d}"
./mylocal-dep14-converter
cd ..
done |& tee dep14-convert.log
```
or similar.
afaict, the main reason for dep-14-convert-git-branch-names to only
output the commands without actually running them, is that there are so
many different workflows/layouts/... and the script tries to produce
sensible commands for *all* of them.
if all your repositories are setup the same, this is a much simpler task.
mfdsa
IOhannes
