It’s more convenient but not necessarily better in terms of git history - for example, it’s very difficult to see exactly when a particular package was changed, and see how it changed, if it’s in a large commit with a commit message of e.g. “Modifications”.
Normally, with git you’d split the commit up into smaller chunks that are more specific, so e.g. a per-package commit. This way it keeps related changes together in one place, and separate from unrelated changes.
Plus, you should work in a “feature branch” for each package, then commit that to master once it’s ready. That way, if you
git pull and there are modifications to the repo it’s unlikely to affect your work and require a merge. If you bunch a large set into one commit you’re much more likely to hit a merge conflict.
cd packages-community/tlp git pull git branch tlp git checkout tlp vim PKGBUILD git add PKGBUILD git commit -S -m "[tlp] Randomly break some systems" git checkout master git pull git merge tlp git push git branch -d tlp