It's probably beyond the scope of the task OP wanted to perform, however this is a much more efficient (and with less downtime on network operations) way to undo unwanted changes than reload in. Example follows.

Lab6#conf t revert timer idle 1
Rollback Confirmed Change: Backing up current running config to disk0:-7
Enter configuration commands, one per line.  End with CNTL/Z.
Lab6(config)#
*Dec 26 19:24:40.127: %ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_BACKUP: Backing up current running config to disk0:-7
*Dec 26 19:24:40.131: %ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_START_IDLETIMER: User: console: Scheduled to rollback to config disk0:-7 if session has been idle for 1 minutes
Lab6(config)#int fa0/1
Lab6(config-if)#shut
Lab6(config-if)#
*Dec 26 19:24:49.035: %LINK-5-CHANGED: Interface FastEthernet0/1, changed state to administratively down
*Dec 26 19:24:50.035: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to down

And after circa 1 minute of session inactivity (suppose you just cut yourself off by performing this shutdown).

Lab6(config-if)#Rollback Confirmed Change: rolling to:disk0:-7
*Dec 26 19:25:46.979: %ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_ROLLBACK_START: Start rolling to: disk0:-7
*Dec 26 19:25:47.047: Rollback:Acquired Configuration lock.
Lab6(config-if)#
!Pass 1
!List of Rollback Commands:
interface FastEthernet0/1
 no shutdown
end


Total number of passes: 1
Rollback Done

*Dec 26 19:25:51.767: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
*Dec 26 19:25:52.835: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to up
*Dec 26 19:25:54.471: %PARSER-6-EXPOSEDLOCKRELEASED: Exclusive configuration lock released from terminal '0' -Process= "Policy Manager", ipl= 0, pid= 28
Lab6(config-if)#