Now, we force update local tracking ref even if we do not force remote ref update. It seems to be sensible approach (C git one) assuming that our repository may be out of sync with the remote one. The potentially lost information here isn't so valuable perhaps. Signed-off-by: Marek Zawirski <marek.zawirski@xxxxxxxxx> --- .../spearce/jgit/transport/RemoteRefUpdate.java | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/org.spearce.jgit/src/org/spearce/jgit/transport/RemoteRefUpdate.java b/org.spearce.jgit/src/org/spearce/jgit/transport/RemoteRefUpdate.java index fd19300..623599f 100644 --- a/org.spearce.jgit/src/org/spearce/jgit/transport/RemoteRefUpdate.java +++ b/org.spearce.jgit/src/org/spearce/jgit/transport/RemoteRefUpdate.java @@ -189,7 +189,7 @@ public RemoteRefUpdate(final Repository localDb, final String srcRef, this.forceUpdate = forceUpdate; if (localName != null && localDb != null) trackingRefUpdate = new TrackingRefUpdate(localDb, localName, - remoteName, forceUpdate, newObjectId, "push"); + remoteName, true, newObjectId, "push"); else trackingRefUpdate = null; this.localDb = localDb; -- 1.5.6.3 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
