Push-to-deploy was implemented in 2.3 and improved in 2.4

diff --git a/pep-git.txt b/pep-git.txt
index d215a585978b640279a538aebed908cc22eeeb05..51701c9935fcb673cade2b5a89fc8ecfa0548fd4 100644 (file)
--- a/pep-git.txt
+++ b/pep-git.txt
@@ -326,6 +326,11 @@ from it) you do that in two steps using two repositories: you push
 from the workstation to a bare repo on the remote host, ssh to the
 remote host and pull from the bare repo to a non-bare deployment repo.
 
 from the workstation to a bare repo on the remote host, ssh to the
 remote host and pull from the bare repo to a non-bare deployment repo.
 

+That changed in git 2.3, but see `the blog post
+<https://github.com/blog/1957-git-2-3-has-been-released#push-to-deploy>`_
+for caveats; in 2.4 the push-to-deploy feature was `further improved
+<https://github.com/blog/1994-git-2-4-atomic-pushes-push-to-deploy-and-more#push-to-deploy-improvements>`_.
+

 Tags
 ''''
 
 Tags
 ''''