Back to issue list Export
Project: Local
Issue: 0401d8ec105816f0f53fdd2ab4b421a610351c2894073d33fb416c2949374dc9
Title:
Date: 2012-08-16 00:28:23
Reported_By: travisb
Seen_In_Build:
Severity: Blocker Critical Major Minor Trivial
Priority: 1 2 3 4 5
State: New Confirmed Open Diagnosed Closed
Resolution: None Fixed Duplicate WontFix Invalid WorksForMe
Type: Bug Feature Regression
Owner: Unassigned travisb stephen@viles.nz
Fix_By: 1.2 Next_Release Eventually 1.0 1.1
Component: Documentation Web_UI VCS Core CLI
Depends_On:
Dependent_Of:
Duplicate_Of:
If the VCS fails to commit, say if there was an out-of-date version, Nitpick doesn't currently tell the user about this fact. This will lead the user to believe that their changes have been committed successfully when they haven't.
This is especially annoying when using a network repository without an operational network.
If the VCS fails to commit, say if there was an out-of-date version, Nitpick doesn't currently tell the user about this fact. This will lead the user to believe that their changes have been committed successfully when they haven't.
Date: 2013-03-08 22:51:30
User: travisb
This is especially annoying when using a network repository without an operational network.