[
https://issues.apache.org/jira/browse/LANG-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372099#comment-16372099
]
ASF GitHub Bot commented on LANG-1373:
--------------------------------------
Github user kinow commented on the issue:
https://github.com/apache/commons-lang/pull/311
I would run something like `git rebase -i HEAD~123` where 123 is the number
of commits I'm going back. Then squash the commits into a single one,
discarding commit messages. Finally, would use a single commit message like
"LANG-1373: The description here...". And then `git fetch --all` followed by a
`git rebase origin/master` to make sure it's at the most recent change in the
remote repository as well. If no merge conflicts, you can simply `push -f` to
your branch, and that should do it.
In case you are concerned about losing your changes, just do from your
branch a `git checkout -b backup-1373` or some other name, `git checkout -` to
go back to your branch, and give it a try (or do it in the other branch,
whichever you prefer)
> Stopwatch based capability for nested, named, timings in a call stack
> ---------------------------------------------------------------------
>
> Key: LANG-1373
> URL: https://issues.apache.org/jira/browse/LANG-1373
> Project: Commons Lang
> Issue Type: New Feature
> Components: lang.time.*
> Reporter: Otto Fowler
> Assignee: Otto Fowler
> Priority: Major
>
> While working on adding some timing functionality to a Metron feature, I came
> across the
> Stopwatch class, but found that it didn’t suite my needs.
> What I wanted to do was to create a timing from a top level function in our
> Stellar dsl, and have have a group of related timings, such that the end
> result was the overall time of the call, and nested timings of other calls
> executed during the dsl execution of that function. These timings would all
> be named, and have a path for identification and include timing the language
> compiler/execution as well as the function execution itself. It would be
> helpful if they were tagged in some way as well, such that the consumer could
> filter during visitation.
> So I have written StackWatch to provide this functionality, and submitted it
> in a Metron PR.
> From the PR description:
> StackWatch
> A set of utility classes under the new package stellar.common.timing have
> been added. These provide the StackWatch functionality.
> StackWatch provides an abstraction over the Apache Commons StopWatch class
> that allows callers to create multiple named and possibly nested timing
> operations.
> <…>
> This class may be more generally useful to this and other projects, but I am
> not sure where it would live since we wouldn’t want it in common.
> StackWatch uses a combination of Deque and a custom Tree implementation to
> create, start and end timing operations.
> A Visitor pattern is also implemented to allow for retrieving the results
> after the completion of the operation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
