how to deprecate addremove

[Christian Boos]

Johannes Stezenbach wrote:
> On Sat, Apr 29, 2006, Thomas Arendsen Hein wrote:
>   
>> * Johannes Stezenbach <js at linuxtv.org> [20060428 17:16]:
>>     
>>> On Fri, Apr 28, 2006, Thomas Arendsen Hein wrote:
>>>       
>>>> "hg ci -A" should continue to work, and this should be enough for
>>>> the most common use of addremove: importing tarballs.
>>>>         
>>> What's wrong with "hg add; hg ci"?
>>>       
>> Sometimes files get deleted, then I want to delete them in the
>> repository, too.
>>     
>
> For importing tarballs deleting isn't necessary.
>   

Sure it is. If you import several tarballs in sequence, in order to track
the history of an external package, you need the automatic removal as well.

Btw, that's why I'm not that happy with the removal of the "addremove"
command, because I think that this command had a clear semantic:
if I were a new user, I certainly would have a harder time to figure out
I have to use "hg add; hg remove --after" for achieving the same task.

So please keep at least the current "hg ci -A" behavior.
"hg addremove" followed by "hg status" was handy to check
what will go in before committing, but I could replace that
with doing "hg ci -A; hg log -rtip" followed by an undo if something
went wrong...

But now that I think about it, "hg log" still doesn't show removed files,
so I'll certainly have to use "hg add; hg remove --after" ...
I'll miss "hg addremove" then.

-- Christian