Was reading the #git update-index manpage for other reasons and discovered the #SplitIndex mode.
This sounds very useful for my huge #GitAnnex archive of pictures, with I think over 100 000 files. A git add can take many seconds in normal mode.
Split index mode allows git to keep a big "static" index and a smaller index that gets updated every time you add/remove/update a file. You can fine-tune how many files need to be updated before the big index is touched.
The feature was added in v2.1.0 in 2014, but v2.22.0 in 2019 are the first release notes not to call it "the experimental split-index mode". The v2.1.0 notes don't even mention the feature at all.
I believe moving over to #Codeberg is a big improvement over relying on #GitHub (which, as #SourceForge once was, is the center of gravity for FOSS projects' development).
I closed all my repos on GH some years back. I kept one or two repos on #BitBucket for years, but they were basically dead. When BB rid itself of #Mercurial ( #hg ) and switched solely to #git, I took advantage of the opportunity to close my account there.
That said, large numbers of people moving en mass from GitHub to Codeberg would just move the problem to a different platform. The problem being people rely heavily on a centralized service.
As for GitHub, I still have my account, and with job-hunting, I really need to put something there. Seriously, I have had some places send rejection notices because they couldn't see any evidence (on GitHub) that I knew anything about the job. But I really only want GH to be a secondary mirror of a main repo hosted elsewhere.
You'll notice that #Git is not in that list. I'm having to use git whenever I deal with other people's code projects, so I already know that it isn't tailored for my needs.
> --fixup=reword:<commit> creates an "amend!" commit which replaces the log message of <commit> with its own log message but makes no changes to the content of <commit>.
@geniusmusing I find #git to be too big and complex for my needs (and arguably for most projects). I know it โwonโ and even some projects that formerly used another #VCS ( such as Mercurial #hg, #darcs, Bazaar #bzr / Breezy #brz ) are switching.
In the plans: a very limited #Kallithea install (with git and Mercurial) and #Fossil for Federati ... when I have more funds and energy to devote to getting it going on its own VPS.
I think yโall know I favor the #Fossil #SCM / #DVCS over #Git (though Iโm giving #Mercurial ( #Hg ) another look as well. Iโm resource-constrained as well as energy-limited, but I have been thinking of standing up a miniature software forge for !FNetworks projects and users, likely using Kallithea (which can use both Hg and Git) and also having some Fossil repos (but not as part of a forge).
Represent Perforce as the first point of contact for customerโs technical requests.
Review and research customer issues to determine and provide the best resolution.
Develop and maintain technical expertise in assigned areas of product functionality and utilize it effectively to help customers.
Resolve database and performance issues.
Research, document, and escalate cases according to procedure.
Provide customer driven feedback to functional areas in order to influence process/product improvements.
Author technical documents on common issues and solutions in order to build the knowledge base.
Positive attitude - Support engineers are required to be respectful, fair, gracious, and knowledgeable.
Create and set up test environments to reproduce and resolve customer issues.
Recreate customer environments to reproduce issues and experiment with possible solutions.
Requirements:
Bachelorโs Degree in Computer Science or similar or relevant work experience
2 or more yearsโ experience providing technical support to enterprise customers
Knowledge of C/C++ and Java and experience with #PHP / #MySQL
Knowledge of Unix & #Linux
Basic networking experience
Experience with Perforce, #Git, or other version control software is desirable
Strong analytics and problem-solving skills
Strong debugging skills
Ability to work in a team environment and contribute ideas and improvements
Able to work well under pressure and prioritize accordingly