with the Linus git, you can git push origin :multiboot_magic and it's gone.
Not quite sure about Ori's git. That's the only way I've done it. I actually have 540 branches at my u-root fork, so I'm hardly a good example. I leave them lying around for reference. On Sun, Jan 12, 2025 at 11:56 AM Paul Lalonde <paul.a.lalo...@gmail.com> wrote: > > Now that I'm doing some daily development, I'm running into process issues > with git. That probably means I'm doing something wrong, and I'm hoping > someone might disabuse me. > > My workflow is to sync my github fork of rminnich/nixos, then git/pull to get > up to date with my repo. I then make a branch for my work: git/branch -b > remotes/origin/regen -n some_feature > After some time, I commit my changes and git/push. I can then generate the > pull request on github and manage the review there, etc, then delete the > branch on github, then 'git/branch regen && git/branch -d some_feature' to > clean up my world. > > This almost works, but leaves a bunch of remotes in my repo: > > fluxcpu% git/branch -a > heads/master > heads/fix_multiboot_magic > heads/keep > heads/_rebase.working > heads/fix_mp_init > heads/some_feature > remotes/origin/master > remotes/origin/regen > remotes/origin/boots > remotes/origin/multiboot_magic > remotes/origin/fix_multiboot_magic > remotes/origin/fix_mp_init > > > What's the right way to clean up these ever-growing remotes? > > Paul > 9fans / 9fans / see discussions + participants + delivery options Permalink ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tc30944502958e1a0-M109728b2986065587044e919 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
