Re: "svn status" does not show unversioned items been deleted but not committed

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: "svn status" does not show unversioned items been deleted but not committed

Andry
So, what about this issues? I see it as not opened yet. Will it be fixed?
Reply | Threaded
Open this post in threaded view
|

RE: "svn status" does not show unversioned items been deleted but not committed

Bert Huijben-5


> -----Original Message-----
> From: Andrey [mailto:[hidden email]]
> Sent: woensdag 14 juni 2017 12:22
> To: [hidden email]
> Subject: Re: "svn status" does not show unversioned items been deleted but
> not committed
>
> So, what about this issues? I see it as not opened yet. Will it be fixed?

It is not easy to really describe 'the issue'.

How would you handle 'svn rm --keep-local <file>', where the current
behavior is the expected behavior.

In Subversion <= 1.6 versioned directories would always be available locally
until the delete was committed and we explicitly handled this case this way.



On the API level there is no real issue, as the information that something
exists locally is already available there...
So the thing that is missing is how to show this information from the 'svn'
tool without breaking backwards compatibility.

        Bert

Reply | Threaded
Open this post in threaded view
|

Re: "svn status" does not show unversioned items been deleted but not committed

Andry
Bert Huijben <[hidden email]> писал(а) в своём письме Wed, 14 Jun 2017  
13:29:18 +0300:

>> So, what about this issues? I see it as not opened yet. Will it be  
>> fixed?
>
> It is not easy to really describe 'the issue'.
>
> How would you handle 'svn rm --keep-local <file>', where the current
> behavior is the expected behavior.
i think `svn status` must at least warn user that deleted file has been  
locally replaced

> In Subversion <= 1.6 versioned directories would always be available  
> locally
> until the delete was committed and we explicitly handled this case this  
> way.
>
>
>
> On the API level there is no real issue, as the information that  
> something
> exists locally is already available there...
> So the thing that is missing is how to show this information from the  
> 'svn'
> tool without breaking backwards compatibility.
>
> Bert
Backwards compatibility is important, availability to loose local changes  
w/o a warning even more important than compatibility
Reply | Threaded
Open this post in threaded view
|

Re: "svn status" does not show unversioned items been deleted but not committed

Daniel Shahaf-2
Andrey wrote on Wed, 14 Jun 2017 14:31 +0300:

> Bert Huijben <[hidden email]> писал(а) в своём письме Wed, 14 Jun 2017  
> 13:29:18 +0300:
>
> >> So, what about this issues? I see it as not opened yet. Will it be  
> >> fixed?
> >
> > It is not easy to really describe 'the issue'.
> >
> > How would you handle 'svn rm --keep-local <file>', where the current
> > behavior is the expected behavior.
> i think `svn status` must at least warn user that deleted file has been  
> locally replaced

The first column of `status` output reports not only the in-wc.db status
(e.g., 'A' / 'D' / 'R'), but also the on-disk status, e.g., '?' and '!'.
For example, compare how after 'svn add iota && /bin/rm iota', iota is
reported with status '!' rather than 'A'.  So I think it would make
sense to have a file that is scheduled to be deleted, but exists on
disk, to be reported as, say, a lowercase 'd'.

If we were designing from scratch, it might have been better to have
two columns — one for the on-disk status and one for the in-db status —
so an added file that exists on disk would be 'AA' and an added file
that is missing would be 'A!', and similarly we could have ' ?' for
unversioned and 'D?' for deleted-in-db-but-exists-on-disk.  That would
have disentangled the overloaded first column.

> Backwards compatibility is important, availability to loose local changes  
> w/o a warning even more important than compatibility

We broke compatibility before, back in 1.6 when we added the seventh
column.  We can decide to do so again.

Why don't we continue this thread on dev@?  This is now a design
question, not a usage question.

Cheers,

Daniel
Reply | Threaded
Open this post in threaded view
|

Re: "svn status" does not show unversioned items been deleted but not committed

Andry
Daniel Shahaf <[hidden email]> писал(а) в своём письме Wed, 14 Jun  
2017 20:47:16 +0300:

> The first column of `status` output reports not only the in-wc.db status
> (e.g., 'A' / 'D' / 'R'), but also the on-disk status, e.g., '?' and '!'.
> For example, compare how after 'svn add iota && /bin/rm iota', iota is
> reported with status '!' rather than 'A'.  So I think it would make
> sense to have a file that is scheduled to be deleted, but exists on
> disk, to be reported as, say, a lowercase 'd'.
In mine case it's `svn remove iota && type nul > iota`
But i think this is almost the same case.