On Wednesday, January 15, 2003, at 09:34 AM, John Barstow wrote:
>>>> 'svn revert' just copies the text-base on top of the working file.
>>>> But the whole point here is that the text-bases are *wrong*.
>>>> wrong in the sense that the text-bases no longer are identical to
>>>> what's in the repository, which is our cardinal rule.
>>> Hmmm... perhaps there should be a command or option that forces an
> update of
>>> the text-base from the repository. After all, your example alters
>>> text-base by hand intentionally, but someone could do that
>>> example, using a wildcard that affects more files than intended.
>> That's why our text-base files end with .svn-base (so they're not
>> easily found by wildcards or 'find'), and why they have read-only
> Just because it's difficult doesn't mean it won't happen. Some
> environments helpfully ask you if you want to override read-only
> when you save a file.
> But if I'm working on a 5,000-file project and the text-base of, say,
> files is corrupted, shouldn't I have the option of forcing a refresh
> of the
> text-base from the server, rather than a)fresh check-out or b)
> attempting to
> figure out what, exactly, is wrong?
I also think this is a good feature. What I'd like is a feature to do
i) check checksums vs text-base. If they differ then mark the file
broken, and optionally contact the repository to fix it.
ii) Contact the repos to verify the checksum of every file. Contact
the repository to fix broken files.
I've mentioned this before, and was told that i) would be an ordinary
part of svn update for files being updated. That's cool. Something to
do ii) would also be nice; maybe as an option to svn cleanup?.
Dr William Uther National ICT Australia
Phone: +61 2 9385 6926 School of Computer Science and
Email: email@example.com University of New South Wales
Jabber: firstname.lastname@example.org Sydney, Australia
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Jan 15 01:04:16 2003