commit 2ef0bd1e53dc9dc1d0f8a2c808790a18c6b5dd0b (patch)
parent 94a15d84cf1844 ops2
tree 6209fd104129bfdc5318fd2cb46b1d3563b5720c
author Jiri Slaby (SUSE) <jirislaby@kernel.org> 2023-01-16 11:08:38 +0100
committer Jiri Slaby (SUSE) <jirislaby@kernel.org> 2025-02-13 13:05:16 +0100
BRANCH_MARKER: work
---
branch/work | 1 +
1 file changed, 1 insertion(+)
diff --git a/branch/work b/branch/work
new file mode 100644
index 00000000000000..587be6b4c3f93f
--- /dev/null
+++ b/branch/work
@@ -0,0 +1 @@
+x
glossary
--------
Commit objects reference one tree, and zero or more parents.
Single parent commits can typically generate a patch in
unified diff format via `git format-patch'.
Multiple parents means the commit is a merge.
Root commits have no ancestor. Note that it is
possible to have multiple root commits when merging independent histories.
Every commit references one top-level tree object.
git clone https://yhbt.net/lore/pub/scm/linux/kernel/git/jirislaby/linux.git