Can this be the expected mapping?
- commit: openSUSE:Factory/firewalld/31.0
merged:
- revert: openSUSE:Factory/firewalld/30.0
- commit: openSUSE:Factory/firewalld/30.0
merged:
…
I liked more when it did not contain the {name}? This makes a pure object access. Now if two files has the same content but different name (LICENSE / license, README / README.txt) but the same content it will create two files.
There are many ways to fix this issue. For now try this one:
- git rebase -i Very carefully, drop the 4 commits that you see here that are from coolo
- :wq
- git fetch --all
- git…
Can be fun to check if this is true, like creating a repo, commiting a file, creating a branch, updating the file in the branch, and create a hard link outside of the repo. If a checkout into…
Do we know how git handles files in its working copy when you e.g. checkout a different branch?
When possible, hardlinks: https://git-scm.com/docs/git-clone/
Can be copying 1.3M files a bit expensive? (I did not measure it, but my crappy HD is killing me every morning)
I think so, right? If we unlink we should be keeping the cached version (copy or link) without risk of changing the content. What do you think?
The problem starts with using "the" in front of "devel project" - because green is KDE:Frameworks5 (the devel project now) and purple is KDE:Frameworks5:LTS (the devel project between august and…
Note that the red line is Factory in the 2nd picture while it's devel branch in the 1st picture.
In the second image the green line is the devel project? What is the 3rd line? For example I…
Idontknow... maybe checkout?
https://gitea.opensuse.org/importers/git-importer/src/branch/main/lib/git.py#L55
I do not understand this as a rebase. IIUC this is setting "refs/heads/{devel,factory}" reference to the parent1 commit, and checking out later this reference.
As datapoint: we're talking about 1.3M files - that would be still ~5000 files per directory. The git objects are packed for a reason - there are not supposed to be 1.3M of them.
In that case…