[Tyler MacDonald]
> I guess my complaint is that the addition of a new feature has
> made something that has worked fine for years and years and years
> just stop. I get bitchy about that sometimes :-)
Sure, I understand the frustration. But --non-interactive was already
a good idea - wha
Hi,
I guess my complaint is that the addition of a new feature has made
something that has worked fine for years and years and years just stop. I
get bitchy about that sometimes :-) This one in particular still _really_
irks me;
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450
[Tyler MacDonald]
> When subversion is being run without a controlling terminal (eg; "svn up <
> /dev/null", or when being executed from a cronjob), subversion should
> realize that it has no controlling terminal and revert to the previous
> default behaviour, "postpone".
The official view: any t
Package: subversion
Version: 1.5.1dfsg1-1
Severity: minor
The previous behaviour of "svn up" was to mark any conflicts in an update as
"postpone".
Now, you have to specifically select "postpone" on a terminal, or pass in
the "--accept postpone" flag to "svn up".
When subversion is being run wit
4 matches
Mail list logo
