tree e6b1a9f600322316b8c6ec742c23065c2ea60bbc
parent 29e1270768f217f7c8471d771d90ff43135d7c26
author Thomas Wolf <thomas.wolf@paranor.ch> 1607438735 +0100
committer Matthias Sohn <matthias.sohn@sap.com> 1607462446 +0100

TagCommand: propagate NO_CHANGE information

Some clients may wish to allow NO_CHANGE lightweight tag updates
without setting the force flag. (For instance EGit does so.)
Command-line git does not allow this.

Propagate the RefUpdate result via the RefAlreadyExistsException.
That way a client has the possibility to catch it and check the
failure reason without having to parse the exception message, and
take appropriate action, like ignoring the exception on NO_CHANGE.

Change-Id: I60e7a15a3c309db4106cab87847a19b6d24866f6
Signed-off-by: Thomas Wolf <thomas.wolf@paranor.ch>