Date: Thu, 8 Apr 2021 22:23:13 -0700 From: Mark Millard <marklmi@yahoo.com> To: simon.wright@gmx.net, FreeBSD ports <freebsd-ports@freebsd.org> Subject: Re: Specific svn/git package update use case Message-ID: <8D6CD370-25E2-42C8-ADC8-B26D187D8577@yahoo.com> References: <8D6CD370-25E2-42C8-ADC8-B26D187D8577.ref@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Simon Wright simon.wright at gmx.net wrote on Fri Apr 9 02:48:47 UTC 2021 : > I'm still not clear though whether checking out this commit brings in > all the commits from git clone to this one or only this commit. My > reading seems to say that this is *only* this one commit which is not my > need. Can anyone confirm this please? [My wording is not trying to be explicit about multi-branch merge points. Nor does it try to deal much with if you have local changes or staged changes in place at the time of the activity or if you have extra files not checked into git in the tree as well. And so on: a simple same-branch context.] A commit hash/id identifies everything on the branch at the time the commit finished, including what did not change compared to the prior commit on the branch. Checking out the commit spans all of it. Jumping forward (or backward) a bunch of commits on a branch does not require doing them one by one to get the net effect. You may want to inspect after checkouts (or similar activity) that "git status" does not display any surprises that need to be cleaned up in the local file system via some variant(s) of git restore or/and git clean or the like. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8D6CD370-25E2-42C8-ADC8-B26D187D8577>