0 views collected around this technical thread.
This article walks through eight typical Git problems—missing branches, unwanted merges, unfinished work, wrong commit messages, early‑stage fixes, mass commit squashing, and recovery after mistakes—showing how to use rebase, cherry‑pick, stash, revert and related commands to resolve them efficiently.
The article explains how InnoDB handles transaction commit by modifying Insert and Update Undo segment states, generating a transaction commit number, adding rollback segments to the purge queue, and finally cleaning or caching Undo segments based on their usage and state.
This article explains comprehensive Git workflow, branch naming conventions, commit message standards, and supporting tools such as validate-branch-name, Husky, Commitizen, and Commitlint, providing practical examples and configuration snippets to help development teams maintain a clean and efficient version‑control process.
This article explains the internal steps InnoDB performs when committing a transaction, covering undo segment caching, generation of the transaction commit number, state changes of insert and update undo segments, history‑list insertion, and the final reinitialisation of the transaction object.
This article explains how MySQL 8.0.32 processes the flush, sync, and commit subphases during a two‑phase commit, detailing the roles of leader and follower threads, log handling, system variables, and the conditions that trigger binlog rotation and persistence.
This article explains MySQL 8.0.32 InnoDB's two‑phase commit process, detailing the flush, sync, and commit sub‑stages, the concept of group commit, and how queues and mutexes coordinate transaction logging to reduce redundant disk writes.
This article explains how to use Git commands to obtain the current commit author, active branch, list of unpushed commits, and the files changed in each commit, and concludes with a promotional notice for a PHP online training class.
This article provides a visual, step‑by‑step guide to the most frequently used Git commands, explaining basic operations like add, commit, reset, and checkout, and detailing advanced actions such as diff, merge, cherry‑pick, and rebase, while illustrating concepts of blobs, trees, and HEAD states.
The article examines how a large transaction in MySQL 5.7 can block the SHOW MASTER STATUS command by holding the lock_log during the commit's flush stage, analyzes the commit and SHOW MASTER STATUS code paths, and proposes mitigation strategies such as avoiding big transactions and using SELECT @@global.gtid_executed.
An AOSP commit proposed by a Xiaomi engineer to prohibit shell extraction of installed APKs—citing potential IP leakage—was rejected after receiving only the author’s support and two opposing votes, with reviewers arguing that such restrictions are ineffective, could be bypassed, and should be handled via DRM or device‑specific policies.
This article provides an in‑depth tutorial on Git, covering its advantages over centralized systems, file states, commit nodes, HEAD, remote repositories, branching strategies, detailed command usage for committing, branching, merging, rebasing, cherry‑picking, and rollback, as well as practical tips for effective version control.
This article presents a detailed collection of 45 everyday Git operations covering commits, amendments, branch management, staging, rebasing, merging, stashing, and recovery techniques, providing clear command examples and explanations to help developers handle typical version‑control tasks efficiently.
This article explains the fundamental Git commands for adding, committing, resetting, checking out, and managing branches, along with detailed descriptions of diff, commit, checkout, reset, merge, cherry-pick, and rebase operations, providing visual illustrations and practical usage tips.
This article explains how Git works internally by describing the .git directory layout, the creation of blob, tree and commit objects during init, add, and commit operations, and how branches, HEAD, remote configuration, reflog, and diff commands manage version history.
This article provides a comprehensive guide to Git's core commands—including add, commit, reset, checkout, merge, rebase, and cherry‑pick—explaining their effects on the working directory, index, and repository, as well as visualizing branch relationships and HEAD states.
This guide explains Git’s core concepts and basic commands—including add, commit, reset, checkout, merge, rebase, and cherry-pick—illustrated with diagrams that show how files move between the working directory, index, and repository, and how branches, HEAD, and detached states operate.
This article provides a comprehensive visual guide to the most frequently used Git commands, explaining their purpose, usage, and effects on the working directory, index, and repository, while illustrating concepts such as commits, branches, merges, rebases, and detached HEAD with clear diagrams.
This article explains how Elasticsearch handles data ingestion, retrieval, and full‑text search by describing the roles of coordinating, primary, and replica nodes, the refresh‑commit‑flush cycle, segment files, translog, and the Lucene‑based inverted index that powers its near‑real‑time capabilities.
This article explains how Git stores data by describing the .git directory layout, the four object types (blob, tree, commit, tag), how objects are hashed and organized, and how Git packs objects to save space, answering why a second commit stores a full file.
This article introduces the basic Git workflow for enterprise developers, covering branch creation, committing changes, and pushing branches to a central repository, with step-by-step command examples and explanations of staging, status, and branch management.