From f02d3336b6cf4859c340a976638f6ab0798cf878 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 17 Apr 2023 14:09:06 -0400 Subject: [PATCH] comment --- ...ent_1_7f9857887a25df617a99cdab119761d8._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/forum/Clarifications_about_how_to_work_with_git-annex/comment_1_7f9857887a25df617a99cdab119761d8._comment diff --git a/doc/forum/Clarifications_about_how_to_work_with_git-annex/comment_1_7f9857887a25df617a99cdab119761d8._comment b/doc/forum/Clarifications_about_how_to_work_with_git-annex/comment_1_7f9857887a25df617a99cdab119761d8._comment new file mode 100644 index 0000000000..0b826d6798 --- /dev/null +++ b/doc/forum/Clarifications_about_how_to_work_with_git-annex/comment_1_7f9857887a25df617a99cdab119761d8._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2023-04-17T18:04:26Z" + content=""" +Just `git pull` the git-annex branch from remotes yourself like any other +git branch. + +git-annex will automatically merge those pulled git-annex branches into its +own local git-annex branch the next time you run it. + +Then you can `git push` the git-annex branch to any remotes you want to +publish updated git-annex information to. +"""]]