Mailing-List: contact dev-help@jmeter.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jmeter.apache.org
From: emilianbold <git@git.apache.org>
To: dev@jmeter.apache.org
Reply-To: dev@jmeter.apache.org
References: <git-pr-300-jmeter@git.apache.org>
In-Reply-To: <git-pr-300-jmeter@git.apache.org>
Subject: [GitHub] jmeter issue #300: Bug 57039 - Inconsistency with the undo/redo log
Content-Type: text/plain
Message-Id: <20170723204331.B3D89E0262@git1-us-west.apache.org>
Date: Sun, 23 Jul 2017 20:43:31 +0000 (UTC)
archived-at: Sun, 23 Jul 2017 20:43:35 -0000

Github user emilianbold commented on the issue:

    https://github.com/apache/jmeter/pull/300
  
    Hm, double-checked now and I still don't see it anymore. Are we looking at the same code? Note that I rebased at some point and did a force push so previous patches might not be identical.
    
    Still, the latest commit ("Add dirty state to the undoable edit...") couldn't have introduced a regression.
    
    
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---