summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2013-11-24 18:19:46 +0100
committerwm4 <wm4@nowhere>2013-12-29 19:25:16 +0100
commitbb41e83d8c32611cceef4dd18f1b7a76f243ceca (patch)
treebd32f0811dda5537763d865dcc3ccf7a4d3c5a3e
parent5ef184443cf40200caf9df5495717c991d5ded7c (diff)
downloadmpv-build-bb41e83d8c32611cceef4dd18f1b7a76f243ceca.tar.bz2
mpv-build-bb41e83d8c32611cceef4dd18f1b7a76f243ceca.tar.xz
README.rst: add a warning about making local changes
-rw-r--r--README.rst12
1 files changed, 12 insertions, 0 deletions
diff --git a/README.rst b/README.rst
index 1cd1536..89d30cc 100644
--- a/README.rst
+++ b/README.rst
@@ -123,6 +123,18 @@ You can build a full mpv Debian package with the following command:
The .deb file will be created in the parent directory. (4 is the number
of jobs running in parallel - you can change it.)
+Local changes to the git repositories
+=====================================
+
+Making local changes to the created git repositories is generally discouraged.
+Updating might remove local changes or conflict with them. Sometimes the
+repositories might be wiped entirely. If you make local changes, always keep
+them in a separate repository and merge them after updating.
+
+In general, changes to the mpv-build repository itself are relatively safe,
+keeping branches in sub-repositories might be ok, and making local, uncommitted
+changes in sub-repositories will break.
+
Forcing master versions of all parts
====================================