public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: PVE development discussion <pve-devel@pve.proxmox.com>
Subject: Re: [pve-devel] Plan for (invasive) shrink of pve-manager git repository
Date: Sun, 28 May 2023 20:51:17 +0200	[thread overview]
Message-ID: <c78db371-a05b-9a3c-a0ae-da324ef1b2d5@proxmox.com> (raw)
In-Reply-To: <2686c33f-a31b-2e3e-1807-fd1640f9ae5b@proxmox.com>

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 --hard origin/master
> 
> Then re-create your active development branches freshly from the master
> and cherry-pick the relevant patches from the old branch.
> 
> After that you can delete the old branches.
> 

Two things I forgot to mention, after above and ensuring no remote or branch
refers to the old git repo anymore, you can use the following to shrink:

git gc --aggressive --prune=now

But, moving the current pve-manager dir to a backup location and just cloning
freshly is waay faster

The other thing was that I had to split out sencha-touch ZIP into it's own repo
before the filter-repo clean up, it lives now in a libjs-sencha-touch package
and its source can be found here: https://git.proxmox.com/?p=sencha-touch.git;a=summary

(and just for completeness sake, note that this was only done for pure compat
reasons only, the mobile UI in PVE that uses it is pretty bare bones and doesn't
gets much love, we should replace it by something slightly more future proof some
day).

cheers,
 Thomas




  reply	other threads:[~2023-05-28 18:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-26  9:45 Thomas Lamprecht
2023-05-28 18:38 ` Thomas Lamprecht
2023-05-28 18:51   ` Thomas Lamprecht [this message]
2023-05-30  8:36   ` Fiona Ebner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c78db371-a05b-9a3c-a0ae-da324ef1b2d5@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=pve-devel@pve.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal