On 08.04.2015 20:00, Evan Driscoll wrote:
> [I typoed some keys and apparently happened to hit send while still
> typing; let's try again. Sorry for the spam.]
>
> On Fri, Apr 3, 2015 at 4:25 PM, Branko Čibej wrote:
>> Would this tell you what you need (given a checkout of 'trunk'):
>>
>> svn
[I typoed some keys and apparently happened to hit send while still
typing; let's try again. Sorry for the spam.]
On Fri, Apr 3, 2015 at 4:25 PM, Branko Čibej wrote:
> Would this tell you what you need (given a checkout of 'trunk'):
>
> svn diff --summarize ^/trunk@ .
>
> This will give you a
On Fri, Apr 3, 2015 at 4:25 PM, Branko Čibej wrote:
> Would this tell you what you need (given a checkout of 'trunk'):
>
> svn diff --summarize ^/trunk@ .
>
> This will give you a summary of the differences between your current
> working copy state and the tree in the repository at .
Sorry fo
On 04/03/15 20:27, Evan Driscoll wrote:
I'd like to put a feature request out there for a --dry-run option to 'svn up'.
There are two things that this would accomplish over 'svn stat --show-updates'.
First, it seems like a natural thing to do; in particular, 'merge'
supports --dry-run and after
On 03.04.2015 21:27, Evan Driscoll wrote:
> I'd like to put a feature request out there for a --dry-run option to 'svn
> up'.
>
> There are two things that this would accomplish over 'svn stat
> --show-updates'.
>
> First, it seems like a natural thing to do; in particular, 'merge'
> supports --d
I'd like to put a feature request out there for a --dry-run option to 'svn up'.
There are two things that this would accomplish over 'svn stat --show-updates'.
First, it seems like a natural thing to do; in particular, 'merge'
supports --dry-run and after using Git for a while my mental model of
