GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

You can think about a Git branch in 3 different ways. way 1: just the commits that "branch" off This is what you're probably thinking about when you `merge` or `rebase` a branch into another one. Git doesn't keep track of which branch another branch is "based" on though: that's why you have to run git merge main (you have to tell it which base branch to merge with!) You can see these commits with: git log main..BRANCHNAME way 2: every previous commit This is what git log BRANCHNAME shows you. When we say a commit is "on" a branch, we mean that it's somewhere in the history for that branch. way 3: just the commit at the end This is how git represents a branch internally. You can run: cat .git/refs/heads/BRANCHNAME to see the commit ID for the branch. That commit's parent (and grandparents, great-grandparents, etc) determine the branch's history.

Download link

https://cdn.masto.host/socialjvnsca/media_attachments/files/111/562/876/113/788/292/original/c491bdc79f22082a.png

Notices where this attachment appears

  1. Embed this notice
    Julia Evans (b0rk@social.jvns.ca)'s status on Tuesday, 12-Dec-2023 09:03:43 JST Julia Evans Julia Evans

    meet the branch

    In conversation Tuesday, 12-Dec-2023 09:03:43 JST from social.jvns.ca permalink
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.