On Fri, Aug 25, 2017 at 10:08:04AM +0100, Julian Foad wrote:
> Example workflow:
>
> 1. There exists a shelved patch 'foo' with a verbose log message
> 2. 'svn unshelve foo'
There can only be one changelist per file.
What if at this point there is another changelist 'bar' which includes a
file mo
On Fri, Aug 25, 2017 at 11:08 AM, Julian Foad wrote:
> Daniel Shahaf wrote:
>> Julian Foad wrote on Thu, 24 Aug 2017 19:46 +0100:
>>> One rough edge is that "unshelving" a patch or finishing/squashing a
>>> checkpoint series simply discards the log message(s). [...]
>>
>> [...] to enable the "long
Daniel Shahaf wrote:
> Julian Foad wrote on Thu, 24 Aug 2017 19:46 +0100:
>> One rough edge is that "unshelving" a patch or finishing/squashing a
>> checkpoint series simply discards the log message(s). [...]
>
> [...] to enable the "long log message" use-case, there should be an easy
> "upgrade p
Julian Foad wrote on Thu, 24 Aug 2017 19:46 +0100:
> I think we will encounter two distinct styles of usage:
>
> * "just put whatever I have aside, I haven't time to think about it
> now, I'll come back to it later" -- no description or just a very brief
> hint, and perhaps not even a name;
>
>
I had some feedback that the ability to give a short description or log
message seemed important, so I have added that feature on the prototype
branches.
$ svn shelve --help
...
1. Save the local changes in the given PATHs to a patch file, and
revert those changes from the WC. If a log mess
5 matches
Mail list logo
