P is for Practical | |
PerlMonks |
Re: [OT] What is best practice for 'git reset'? (updated)by haukex (Archbishop) |
on Apr 20, 2017 at 13:46 UTC ( [id://1188409]=note: print w/replies, xml ) | Need Help?? |
Not a git expert, but a quick test seemed to show me that git reset --soft 2.12_002 will leave the changes from the newer versions in the index, I don't think that's what you want, because a commit afterwards would put those changes back into the repo. If you want to begin your work with a commit that undoes all the changes since 2.12_002, the following seems to work, even directly on master.
Another approach might be to base the new branch on 2.12_002 and then later merge that branch back into master,
Update: Here's how I generated the fake repo for testing:
And similarly the fake edit:
Update 2017-04-21: Just noticed this cross-posting to perl.module-authors. Also, it appears we're talking about File::Path version 2.12_004 (GitHub).
In Section
Seekers of Perl Wisdom
|
|