Date: Thu, 28 Sep 2023 15:59:08 +0200 From: Ede Wolf <listac@nebelschwaden.de> To: questions@freebsd.org Subject: Re: resync ports? Message-ID: <a7034fea-c36f-4d7d-a000-0cbe5819ad5c@nebelschwaden.de> In-Reply-To: <6C137DA9-2BF8-49EC-8086-CCDB3A3E64A7@gushi.org> References: <d929aeb5-5b60-492d-84db-d0134eec68ec@nebelschwaden.de> <6C137DA9-2BF8-49EC-8086-CCDB3A3E64A7@gushi.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the link! git stash seems to do the trick - maybe in conjuction with a prior git reset, I will have an eye on this Am 27.09.23 um 22:12 schrieb Dan Mahoney (Ports): > You’re looking for git reset —hard > > > > Git - git-reset Documentation <https://git-scm.com/docs/git-reset>; > git-scm.com <https://git-scm.com/docs/git-reset>; > favicon.ico <https://git-scm.com/docs/git-reset>; > > <https://git-scm.com/docs/git-reset>; > > -Dan > >> On Sep 27, 2023, at 12:41 PM, Ede Wolf <listac@nebelschwaden.de> wrote: >> >> Hello, >> >> I had to make a change to a makefile to make that port compile. Now I >> am wondering how to get the original makefile back, in a way that it >> is controlled by git again? >> >> Somehow I expected git pull to work like rsync, but it is obviously not. >> >> The question that emerges, is there a more resourcefriendly way to get >> my portstree back in sync with git without a new full checkout? >> >> Thanks >> >> Ede >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a7034fea-c36f-4d7d-a000-0cbe5819ad5c>