Am 28.05.23 um 20:38 schrieb Thomas Lamprecht:
> If you fetch in an existing pve-manager.git repository you'll see something
> like:
> From git://git.proxmox.com/git/pve-manager
> + f548e4fca...4a8501a8b master -> origin/master (forced update)
> + 40ccc11c4...d26a7c43e stable-3 ->
Am 28/05/2023 um 20:38 schrieb Thomas Lamprecht:
> For re-aligning your local master branch you can do a hard-reset, BUT check
> if you got any local commits yet (move them over to another branch with e.g.
> `git checkout -b feature-to-re-apply-on-master`
>
> git checkout master
> git reset
Am 26/05/2023 um 11:45 schrieb Thomas Lamprecht:
> I'll use the git filter-repo [0] tool, a replacement for filter-branch with
> better UX and less potential for getting it wrong, to rewrite the history,
> filtering out any problematic artefact or directory.
>
> For this I'll use the following
Hi all!
It follows a head's up for the plan of making it easier to work with our
pve-manager git repository by rewriting its history to filter out huge
artefacts.
This will only affect developers, nothing in the current pve-manager Debian
package will change.
# Background
Our current
