|There's more than one way to do things|
What is best practice for 'git reset'?by jkeenan1 (Deacon)
|on Apr 20, 2017 at 11:47 UTC||Need Help??|
jkeenan1 has asked for the wisdom of the Perl Monks concerning the following question:
I am maintainer of a CPAN distribution whose most recent official release is version 2.12.
Since 2.12 was published, we have made the following development releases:
In the git repository, we have tags for:
(Somehow 2.12_001 was overlooked or has not yet been set.)
I now realize that much of the code (mostly tests, but some source) added in 2.12_003 and 2.12_004 is conceptually flawed. For other developers and myself to treat 2.12_004 as the starting point for future development would not be fruitful.
What I would like to do is to go back to 2.12_002 and start development anew from there -- but without pretending that 2.12_003 and 2.12_004 were never released. I would like 2.12_005 to be equivalent to 2.12_002 but with only very safe, minor touchups.
Would the following be the recommended sequence of git commands?
Thank you very much.