Git Rev News

> Given that the "master" in historic VCS programs (like Bitkeeper) is explicitly based on master/slave terminology, that git deliberately picked the term to maintain continuity of context with other VCS systems... While some VCS programs may have used master/slave (I think maybe CVS did?), BitKeeper did not. The (likely) basis for the belief that BitKeeper use master/slave and git followed them, the GNOME mailing list post[0] that reignited this discussion in 2019, was retracted the next year[1]. I wrote a summary of the history[2] for Git Rev News, the git developers newsletter. In short, the usage didn't come from BitKeeper, and was intended to mean 'master copy'. After the article was published, Aaron Kushner from BitKeeper reached out and gave me some more history on the usage of 'slave repository' in that one particular spot in BitKeeper[3]: it was a presentation for a client that was already using master/slave terminology and so the same terms were used in the presentation. 0: https://mail.gnome.org/archives/desktop-devel-list/2019-May/msg00066.h… 1: https://mail.gnome.org/archives/desktop-devel-list/2020-June/msg00023.… 2: https://git.github.io/rev_news/2020/07/29/edition-65/ 3: https://twitter.com/AndrewArdill/status/1350537333292949505

The whole point of the article is that not everyone is a [professional] "dev/SWE", or in other words: > ...a bunch of people who are already really comfortable with their terminals, and they’re reading the email from mailing lists in their terminals already, and unpacking patches by typing out a tar command in a single go. But even if you consider the case of "lazy" devs, I think the conclusion holds true: > I guess this short TL;DR version would be I feel that version control systems (the next version of them) should not be something that was specifically made for the Linux Kernel community. It should be something that was specifically designed to be used by the wider community. It has become the de facto distributed version-control system for the world, but if even people who are "highly paid" professionals struggle with the CLI, what hope for everyone else? It might only be "semi-complex" to you, but there are dozens of GUIs listed on official site[0], dozens of books teaching it and an official manual which is still a "work in progress"[1] 15 years after it was released suggesting a different view in the wider community. Imagine if git was lost and it had to be recreated, would it make sense to rebuild it exactly as it is now? It's an amazing tool and has stretched far beyond it's original use case, but surely we can all agree that there is room for improvement in its design? [0] https://git-scm.com/downloads/guis [1]…

My anecdotal experience is that I indirectly need/benefit from rerere much less often because I'm not usually resolving the same specific conflict more than once. I fix it the one time and then jj is rebasing a whole lineage for me, starting from the early commits, not from the single-branch leaves. That way I don't get "I rebased one branch and fixed this one already, but now I have to do it again for a second branch that shared the same conflicted commit as the first." By contrast, git rebase --update-refs does not handle sibling branches but detaches them instead, and git replay hasn't had much TLC for UX yet. Plus, the last time I tried replay it was still obliterating commit signatures. https://git.github.io/htmldocs/git-replay.html

I would have thought for sure someone would have already tried that, but regrettably trying to search for "serverless git" coughs up innumerable references to the framework that is hosted on GIThub Anyway, I was curious how much work such a stunt would be and based on the git-http-backend docs <https://git.github.io/git-scm.com/docs/git-http-backend#Documentation/… it seems like there are actually a manageable number of endpoints I actually prefer their second scenario of splitting out access to the objects and pack files but since doing that would still require a function (or, ahem, a web server running) I suspect that optimization is not within the scope of what you had in mind

Found on https://git.github.io/rev_news/2023/09/30/edition-103/

Hmmm, kind of misleading name. This isn't "git" news. It's miscellaneous software projects. If you want actual git news, checkout https://git.github.io/rev_news/

Url changed from https://git.github.io/rev_news/2018/08/22/edition-42/, which points to this.

In Git Rev News edition 20 (https://git.github.io/rev_news/2016/10/19/edition-20/) there are also articles about some changes in v2.11: - Changing the default for “core.abbrev”? - Prepare the sequencer for the upcoming rebase -i patches (I am a Git Rev News editor.)

There is now at least an RSS option: http://git.github.io/feed.xml Mail subscription is in the works.

Location: India Remote: Yes (open to Anything) Willing to relocate: Yes • Languages & Frameworks: Go, Python, Ruby, C, gRPC, Protocol Buffers, Rails, Django • Tools & Platforms: Git, Docker, Kubernetes, Terraform, Google Cloud Platform (GCP), AWS, Terraform, Apache Spark • Databases: MySQL, PostgreSQL, MongoDB, Redis, BigQuery, Redshift, Snowflake, Databricks, PowerBI, Dataflow, Looker • Monitoring & CI/CD: Stackdriver, Datadog, Prometheus, Grafana, Circle CI, Argo Workflows Resume: https://drive.google.com/drive/folders/1mpL6L-fCUpg4xIXztJ3v2sfaEw0C71… LinkedIn: https://www.linkedin.com/in/edith007/ Email: [email protected] Hi I am Siddharth, and I am looking for full time opportunity for Software Engineer Role. I want to share not just my past achievements but also what I’ve been working on recently as a Software Engineer at Atlan. Right from my first weekend, I jumped in, handling support tickets and quickly becoming a top performer in multiple support cycles. I showed I could meet tight deadlines by creating the company’s first 10-day connector in just 9 days. I also played a key role in speeding up our Snowflake & PowerBI workflows, cutting the runtime by 96%, which made a huge difference in our system’s efficiency. One of my big wins was improving system observability. I used Stackdriver, Datadog, Grafana, Prometheus, and Elasticsearch to enhance monitoring and alert handling, which really boosted customer satisfaction. I also optimized…