This is an automated email from the ASF dual-hosted git repository.

elharo pushed a change to branch deps
in repository https://gitbox.apache.org/repos/asf/maven-scm.git


 discard 1299da5f7 sshd-osgi
 discard 95702fe68 fix
 discard 19dc85a62 2.14.0
 discard 49efa15ff fix
 discard 4e66c24d6 fix
 discard 43e1a5e94 Declare used dependencies
     add 5c7616edf Prefer try with resources (#228)
     add ed4c7f7fc Declare used dependencies
     add 870928736 fix
     add ece71fd97 fix
     add 4f325abbe 2.14.0
     add b4fcd450e fix
     add 7a50d10f2 sshd-osgi

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (1299da5f7)
            \
             N -- N -- N   refs/heads/deps (7a50d10f2)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:
 .../org/apache/maven/scm/util/ConsumerUtils.java   | 11 ++----
 .../local/metadata/LocalScmMetadataUtils.java      | 22 +++++-------
 .../checkout/LocalCheckOutCommandTckTest.java      | 20 +++++------
 .../command/update/LocalUpdateCommandTckTest.java  | 19 ++++------
 .../git/jgit/command/branch/JGitBranchCommand.java |  6 +---
 .../JGitCheckInCommandCommitterAuthorTckTest.java  |  9 +----
 .../svn/svnexe/command/SvnCommandLineUtils.java    |  7 ++--
 .../tck/command/branch/BranchCommandTckTest.java   | 14 ++++----
 .../tck/command/checkin/CheckInCommandTckTest.java | 41 ++++++----------------
 .../scm/tck/command/tag/TagCommandTckTest.java     | 14 ++++----
 10 files changed, 54 insertions(+), 109 deletions(-)

Reply via email to