Specific svn/git package update use case

[Simon Wright]

Thank you. I had to delete and recreate the repro as non-shallow to get
the commit history but once done then I could find the commit and update
to it.

Follow-up:
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?

Second follow-up:

After the checkout I receive this message:
==================
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

   git switch -c <new-branch-name>

Or undo this operation with:

   git switch -

Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at c3c627b0656 devel/jenkins-lts: Update to 2.277.2
==================

I don't want to create a new branch but "fix" or merge the checkout into
my local branch? Or can I just leave it as is?

Thanks,

Simon.


On 09/04/2021 9:02 am, Masachika ISHIZUKA wrote:
>> [/share/freebsd_ports] # git pull c3c627b06563
>> fatal: 'c3c627b06563' does not appear to be a git repository
>> fatal: Could not read from remote repository.
>
> First, check the commit.
> % git log| grep c3c627b06563
> commit c3c627b06563cd0c7bcc4f491cd9c6f50716033b
>
> Then checkout it.
> % git checkout c3c627b06563cd0c7bcc4f491cd9c6f50716033b
>