diff options
| author | Fernando Apesteguía <fernape@FreeBSD.org> | 2022-09-30 08:20:48 +0000 |
|---|---|---|
| committer | Fernando Apesteguía <fernape@FreeBSD.org> | 2022-09-30 08:20:48 +0000 |
| commit | fb40f7a6d80b21aa0da2d2ed43c9e9051b3e3f8b (patch) | |
| tree | c909e69e26a4bbebd4b3be6bb603f857e3f1b0a5 /documentation/content/en/articles/committers-guide | |
| parent | 8321c86562b4957414141909b0d57dac66494ed5 (diff) | |
Diffstat (limited to 'documentation/content/en/articles/committers-guide')
| -rw-r--r-- | documentation/content/en/articles/committers-guide/_index.adoc | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/documentation/content/en/articles/committers-guide/_index.adoc b/documentation/content/en/articles/committers-guide/_index.adoc index 216afb4458..52aa7d887f 100644 --- a/documentation/content/en/articles/committers-guide/_index.adoc +++ b/documentation/content/en/articles/committers-guide/_index.adoc @@ -769,6 +769,7 @@ Git differs from other version control systems in that you have to tell it expli I have opted to do it on the commit command line, but you can also do it with 'git add' which many of the more in depth tutorials cover. ====== Time to update + When it is time to bring in a new version, it is almost the same as w/o the branches. You would update like you would above, but there is one extra command before you update, and one after. The following assumes you are starting with an unmodified tree. |