From 7fafd37298c706aee0895451c3d709adca058202 Mon Sep 17 00:00:00 2001 From: Stefan Beller Date: Mon, 12 Jan 2015 16:49:21 -0800 Subject: [PATCH] Update atomic constant The atomic feature is now cooking in -next in git-core. Very rarely features are ejected from the the next branch in git-core, so I consider it reasonable to come up with this patch now to make the 2 implementations interoperable. Change-Id: I806a8ae3c045ca5936f69cb903baf9b99ee39181 Signed-off-by: Stefan Beller --- .../src/org/eclipse/jgit/transport/GitProtocolConstants.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/org.eclipse.jgit/src/org/eclipse/jgit/transport/GitProtocolConstants.java b/org.eclipse.jgit/src/org/eclipse/jgit/transport/GitProtocolConstants.java index 9ec14aade..976a82361 100644 --- a/org.eclipse.jgit/src/org/eclipse/jgit/transport/GitProtocolConstants.java +++ b/org.eclipse.jgit/src/org/eclipse/jgit/transport/GitProtocolConstants.java @@ -142,7 +142,7 @@ public class GitProtocolConstants { * * @since 3.6 */ - public static final String CAPABILITY_ATOMIC = "atomic-push"; //$NON-NLS-1$ + public static final String CAPABILITY_ATOMIC = "atomic"; //$NON-NLS-1$ /** * The client expects a status report after the server processes the pack.