| commit | cdd6afe03a0a91766cfe73228759d5abd6fad6e8 | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Tue, 23 Dec 2008 00:27:21 +0000 (22 16:27 -0800) | ||
| committer | Robin Rosenberg <robin.rosenberg@dewire.com> | |
| Sun, 4 Jan 2009 00:01:49 +0000 (4 01:01 +0100) | ||
| tree | 54d46aea24a8c051f5e9d34ff9d6d525297630d2 | treesnapshot (tar.gz zip) |
| parent | ab75ea7579605174e463fae0d267450ffa0dd6a4 | commitdiff |
Allow null new ObjectId during RefUpdate.delete
If we are deleting a ref we really don't care about what the
new ObjectId value should be; it just doesn't matter. If we
didn't set the value we should consider it the same as if we
had a MissingObjectException, which means treat the value as
null and perform a force update test.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com>
If we are deleting a ref we really don't care about what the
new ObjectId value should be; it just doesn't matter. If we
didn't set the value we should consider it the same as if we
had a MissingObjectException, which means treat the value as
null and perform a force update test.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com>
| org.spearce.jgit/src/org/spearce/jgit/lib/RefUpdate.java | diffblobblamehistory |