On 3/2/2016 7:44 AM, Andy Bradford wrote:
Are there any other issues that could be addressed in the stash-fixes branch? If not, I would like to merge it. Basically it cleans up the ability to stash a rename.
One of the changes was to the schema of the table used by the stash in the local (per checkout) database, which was going to require that every open checkout be re-opened.
Would it be preferred for fossil stash to check for that schema change and automatically fix the open checkout if needed?
As I understand it, "fossil close && fossil open" would result in loss of an existing stash.
We need the fix for rename, but it should be gentler for a user. -- Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.com/ +1 626 303 1602 _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
