Re: Checkpointing v1 design -- terminology

2017-11-10 Thread Paul Hammant
> > $ svn save --revert -v2 "add hair color to person page" >> >> .. does the save and THEN drops the CL and it's changes in working copy - >> back to no changes but not necessarily up to date. >> > > That sounds like you're proposing an alternative syntax for what the > 'shelve' command does -- ex

Re: Checkpointing v1 design -- terminology

2017-11-10 Thread Branko Čibej
On 10.11.2017 14:20, Julian Foad wrote: > Julian Foad wrote: >> [...] To achieve such rollbacks, the user would have to first revert, >> which involves deciding what to revert. >> >> And that seems OK to me. > > The larger point is that this kind of work flow, and the difficulty of > working with c

Re: Checkpointing v1 design -- terminology

2017-11-10 Thread Julian Foad
Julian Foad wrote: [...] To achieve such rollbacks, the user would have to first revert, which involves deciding what to revert. And that seems OK to me. The larger point is that this kind of work flow, and the difficulty of working with changes in overlapping subtrees, is analogous to some

Re: Checkpointing v1 design -- terminology

2017-11-10 Thread Julian Foad
Paul Hammant wrote: I'd be happier with save-cl rather than ci-save.  Or just 'save', as I'm not sure what you're saving if not a change list.  Incidentally CL looks pretty close to CI in lower case and that's already used. Spaces allowed in FOO name? $ svn save -v2 "add hair color to person