You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flagon.apache.org by jk...@apache.org on 2023/10/04 17:44:49 UTC

[flagon-distill] branch 0.0.6 updated (4698e04 -> 9eabe28)

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

jky pushed a change to branch 0.0.6
in repository https://gitbox.apache.org/repos/asf/flagon-distill.git


 discard 4698e04  docs(readme): fixed repo url and name
 discard d53211c  test(test_segment): adds specified default for the newline behavior on the exported csv in export_segment; changes the file opener in test_segment to a proper context manager so the file closes on context exit
 discard 5518d07  ci(bump-version): remove dependency on RAT
 discard cafa1ad  ci(bump-version): triggers action run on PR into dev
 discard 471e28e  ci(bump-version): Removes bump commit message restrain to trigger commitizen
 discard 965aa59  ci(bump-version): adjusts the cz version bump and changelog to all PRs into dev
     add 7dc4323  ci(bump-version): adjusts the cz version bump and changelog to all PRs into dev
     add 3bc4b0c  ci(bump-version): Removes bump commit message restrain to trigger commitizen
     add ffdacbe  ci(bump-version): triggers action run on PR into dev
     add a89c9f2  ci(bump-version): remove dependency on RAT
     add 2389540  Merge pull request #35 from UMD-ARLIS/34-changelog-bump
     add 27ca591  test(test_segment): adds specified default for the newline behavior on the exported csv in export_segment; changes the file opener in test_segment to a proper context manager so the file closes on context exit
     add 9058a1f  docs(readme): fixed repo url and name
     add 16832e7  Merge remote-tracking branch 'apache/master' into 37-export-segment-test-failures-on-windows
     add b603d01  Merge pull request #38 from UMD-ARLIS/37-export-segment-test-failures-on-windows
     add 9eabe28  Merge pull request #17 from UMD-ARLIS/dev

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   (4698e04)
            \
             N -- N -- N   refs/heads/0.0.6 (9eabe28)

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: