Re: [TSVN] commit of missing files automatically selects removal

On 9/30/05, Matthias Wächter <matthias.waechter@tttech.com> wrote:
> Another question (without the old issue with disabled dragging and
> copy/paste solved):
>
> In our project, we have a directory containing .tex files that are
> make-d to a .pdf file. This pdf file is also tracked under version
> control. Issuing a "make clean" removes this pdf file.
>
> In such a situation, if someone wants to commit the contents of the
> current folder, TSVN assumes that the missing pdf file wants to be
> removed and checks the checkbox. If someone forgets to uncheck this box,
> the file is removed from the repository. grrr. Some person then has to
> actually notice this fault and replace the file.
>
> What's the logic behind automatically selecting missing files for
> removal? I mean, if a new file is present it's not selected for addition
> either, sure, but why *automatically* remove (or select for removal) a
> file that's actually under version control? Shouldn't the tool be more
> careful and require *explicit* action of the user if an operation like
> removal is to be done on a file under version control?

Because:
1. Many people are lazy and just delete files in explorer, without
using the "remove" command from the context menu
2. People insisted that those entries are checked by default
3. If a file is missing, you don't need it anymore - so why leave it
in working copies of others? That just will lead to broken builds.

The real question you should ask yourself: why do you have a
*generated* file under version control???

Stefan

--
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org