Re: [Development] How to use `init-repository` properly to clean up the working tree after checking out?

On Tuesday, 22 August 2023 23:35:56 PDT Haowei Hsu wrote: > Hello, Thiago. > > > No, I mean, why do you want to get Qt 6.2.4 in the first place? > > I didn't say that it had to be *6.2.4*. In fact, I've also tried to build > other Qt6 releases, such as: *6.1, 6.3, 6.5*... etc. And have you

Re: [Development] How to use `init-repository` properly to clean up the working tree after checking out?

On 23 Aug 2023, at 08:35, Haowei Hsu wrote: Hello, Thiago. No, I mean, why do you want to get Qt 6.2.4 in the first place? I didn't say that it had to be 6.2.4. In fact, I've also tried to build other Qt6 releases, such as: 6.1, 6.3, 6.5... etc. However, I found during the process that when

Re: [Development] How to use `init-repository` properly to clean up the working tree after checking out?

Hello, Thiago. > No, I mean, why do you want to get Qt 6.2.4 in the first place? I didn't say that it had to be *6.2.4*. In fact, I've also tried to build other Qt6 releases, such as: *6.1, 6.3, 6.5*... etc. However, I found during the process that when I initialize submodules in the *dev*

Re: [Development] How to use `init-repository` properly to clean up the working tree after checking out?

On Tuesday, 22 August 2023 21:05:19 PDT Haowei Hsu wrote: > Hello, Thiago. > > > Why? > > Take CMake for example. No, I mean, why do you want to get Qt 6.2.4 in the first place? You're having a Git problem that happens with Qt repositories but is not Qt's fault. I'm not interested in

Re: [Development] How to use `init-repository` properly to clean up the working tree after checking out?

Hello, Thiago. > Why? Take CMake for example. If I want to build its *3.25.0* release from sources, there are mainly 2 options to acquire 3.25.0 release's sources: 1. Git clone the whole CMake repository, and then checkout to the v3.25.0 tag. 2.

Re: [Development] How to use `init-repository` properly to clean up the working tree after checking out?

On Tuesday, 22 August 2023 07:48:53 PDT Haowei Hsu wrote: > Therefore, I want to > find a way to switch 'qt/qt5' from a branch/tag to another branch/tag just > like we do in > other Git repositories. Why? -- Thiago Macieira - thiago.macieira (AT) intel.com Cloud Software Architect - Intel

Re: [Development] How to use `init-repository` properly to clean up the working tree after checking out?

Hello, Kai. Haowei, you seem to have found the solution yourself previously: git clean > -xfdf. > The problem of my solution is that it cannot remove qtlocation and qtspeech, either. Or just clone Qt 6.2.4 (and other branches/tags) in a separate git checkout > directory. If possible, I don't

Re: [Development] How to use `init-repository` properly to clean up the working tree after checking out?

> The question you must answer is why git > submodule update isn't checking those > commits out for those submodules. > > Anyway, why are you checking out 6.2.4 using Git? That's the key: qtlocation and qtspeech weren't part of 6.2 qt5.git. So when switching from dev to 6.2.4, 'git checkout'

Re: [Development] How to use `init-repository` properly to clean up the working tree after checking out?

On Sunday, 20 August 2023 21:41:02 PDT Haowei Hsu wrote: > The following attachment, *log-git-ls-tree.txt*, is the log that I run *`git > ls-tree @`* command. > Can you discern any clues from this? No. That tells us what commit they should be in, but that's information I already had (because I

Re: [Development] How to use `init-repository` properly to clean up the working tree after checking out?

Hello, Thiago. The following attachment, *log-git-ls-tree.txt*, is the log that I run *`git ls-tree @`* command. Can you discern any clues from this? BTW, The remote URL I used to git clone qt5 is from GitHub: - https://github.com/qt/qt5.git And it seems that the default remote URL that

Re: [Development] How to use `init-repository` properly to clean up the working tree after checking out?

On Sunday, 20 August 2023 20:45:58 PDT Haowei Hsu wrote: > Hello, Thiago. > > Strange to say, when checking out to the submodules and run *`git status`*, > they all say that the *working tree is clean*. The issue is not that they are dirty, but that those submodules are in the wrong commit. To

Re: [Development] How to use `init-repository` properly to clean up the working tree after checking out?

Hello, Thiago. Strange to say, when checking out to the submodules and run *`git status`*, they all say that the *working tree is clean*. *C:\Users\hwhsu1231>chdir /d D:\Repo\tmp\qtD:\Repo\tmp\qt>git statusOn branch 6.2.4Your branch is up to date with

Re: [Development] How to use `init-repository` properly to clean up the working tree after checking out?

On Sunday, 20 August 2023 12:18:24 PDT Haowei Hsu wrote: > If the screenshots are too small for you to see, you can click/download > the attachment I uploaded: > >- *log-init-repository-not-able-to-clean-up.txt* >- *log-my-approach-to-clean-up.txt* > > Because those screenshots are taken

Re: [Development] How to use `init-repository` properly to clean up the working tree after checking out?

Hello, Thiago. Thanks for your reply. If the screenshots are too small for you to see, you can click/download the attachment I uploaded: - *log-init-repository-not-able-to-clean-up.txt* - *log-my-approach-to-clean-up.txt* Because those screenshots are taken from them. --- Haowei Hsu

Re: [Development] How to use `init-repository` properly to clean up the working tree after checking out?

On Sunday, 20 August 2023 10:41:37 PDT Haowei Hsu wrote: > However, I found that even after I run *`perl init-repository -f`* and then > running *`git status`* > again, the working tree is still not clean. Use "git submodule update --recursive" instead > Currently, whenever I check out to