Add support for logAllRefUpdates configuration parameter
Honor the configuration parameter core.logAllRefUpdates when writing reflogs. Instead of writing reflog entries always only write reflogs if this parameter is set to true or if the corresponding file in the <git-dir>/logs directory already exists. In other words: if you are updating a ref and this parameter is set to false and there is no file corresponding to your ref in the <git-dir>/logs folder then no reflog will be written. This is a fix for the issue http://code.google.com/p/egit/issues/detail?id=4 Change-Id: I908e4c77e3630dc3223b2d2a47cb4534dbe4ed42 Signed-off-by:Matthias Sohn <matthias.sohn@sap.com> Signed-off-by:
Christian Halstrick <christian.halstrick@sap.com> Signed-off-by:
Shawn O. Pearce <spearce@spearce.org>
Showing
- org.eclipse.jgit.test/tst/org/eclipse/jgit/lib/ReflogConfigTest.java 122 additions, 0 deletions....jgit.test/tst/org/eclipse/jgit/lib/ReflogConfigTest.java
- org.eclipse.jgit/src/org/eclipse/jgit/lib/CoreConfig.java 11 additions, 0 deletionsorg.eclipse.jgit/src/org/eclipse/jgit/lib/CoreConfig.java
- org.eclipse.jgit/src/org/eclipse/jgit/lib/RefLogWriter.java 11 additions, 8 deletionsorg.eclipse.jgit/src/org/eclipse/jgit/lib/RefLogWriter.java
- org.eclipse.jgit/src/org/eclipse/jgit/lib/Repository.java 1 addition, 0 deletionsorg.eclipse.jgit/src/org/eclipse/jgit/lib/Repository.java
Loading
Please register or sign in to comment