[MERGE] Implement the oft-discussed automatic-add-and-delete at commit time.
Martin Pool
mbp at canonical.com
Wed Aug 6 06:01:05 BST 2008
On Wed, Aug 6, 2008 at 2:43 PM, Aaron Bentley <aaron at aaronbentley.com> wrote:
> Robert Collins wrote:
>> On Tue, 2008-08-05 at 07:59 -0400, Aaron Bentley wrote:
>>
>>> Am I correctly understanding that this patch takes away the ability to
>>> have auto-delete without auto-add?
>>>
>>> If so, DO NOT WANT.
>>
>> Yes, it does.
>>
>> Why is auto-delete better/safer than auto-add?
>
> - - I often have files in my tree temporarily that I do not want to add
> - - the standard mv command would cause a delete and add, which is a bad
> failure mode
> - - I have much stronger control over which files are deleted from my tree
> than which files are added to my tree.
>
>> Also, assuming that it makes sense to allow automatic add (I believe it
>> does), how to present this - what options/flags etc should we have.
>
> I don't necessarily agree that it makes sense. Maybe for scripting. I
> guess --auto-add would work. But for scripting, "bzr add && bzr commit"
> is sufficient.
I'd like to see separate --auto-add and --auto-remove, and perhaps an
--auto-add-remove == -A which turns them both on.
Possibly commit should also print the names of unknown files as it
skips them as a reminder that they're there? I do fairly often forget
to add new files, and then need to uncommit to put them in.
--
Martin <http://launchpad.net/~mbp/>
More information about the bazaar
mailing list