Sounds like someone might have checked in some files they shouldn't have
or neglected to check them in previously.
In any event, if you haven't modified any files in your source tree, you
can run:
$ git reset --hard release-3.4.1
That will make your tree look like release-3.4.1, regardless of
Bernhard schrieb am 07.02.21 um 09:06:
Hi
I'm also only a casual user of git/github, but
Bruce Williams schrieb am 07.02.21 um 03:17:
So, I did this:
bruce@admin:~/Downloads/darktable-dev/darktable$ git checkout
release-3.4.1
error: The following untracked working tree files would be
Hi
I'm also only a casual user of git/github, but
Bruce Williams schrieb am 07.02.21 um 03:17:
So, I did this:
bruce@admin:~/Downloads/darktable-dev/darktable$ git checkout release-3.4.1
error: The following untracked working tree files would be overwritten by
checkout:
> Can someone explain why when I do:
>
> bruce@admin:~/Downloads/darktable-dev/darktable$ git branch
> * master
>
> ...all I see is master?
>
When you cloned darktable's repository from Github you got only the master
branch (wich is the default behaviour). "git branch" shows you only local
So, I did this:
bruce@admin:~/Downloads/darktable-dev/darktable$ git checkout release-3.4.1
error: The following untracked working tree files would be overwritten by
checkout:
src/tests/integration/-nop/expected.png
src/tests/integration/-nop/nop.xmp
"git tag" will show you the releases:
...release-3.2.0
release-3.2.1
release-3.3.0
release-3.4.0
release-3.4.1
release-3.5.0
You can then "git checkout release-3.4.1" to get the files in your
working directory to match those of the release.
On 7/02/21 1:23 pm, Bruce Williams wrote:
> Hi all,
>
Hi all,
Still trying to wrap my head around using github.
Can someone explain why when I do:
bruce@admin:~/Downloads/darktable-dev/darktable$ git branch
* master
...all I see is master?
I expected to see a branch for 3.4.1
Am I misunderstanding something here?
Cheers,
Bruce Williams
