Bazaar

Why doesn't 'commit' run the 'add' command automatically?

Asked by Jon Loldrup

Just wondering.. any good reason?

Question information

Language:
English Edit question
Status:
Answered
For:
Bazaar Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Vincent Ladeuil (vila) said : 		#1

Because 'add' can't be run blindly most of the time. And because the *intent* of 'add' and 'commit' are different.

'add' intent is to inform bzr that new files should be versioned.

'commit' intent is to record a set of changes to a working tree and creates a new revision. In most cases this is done after *validation* by the user that the set of changes is the intended one.

Revision history for this message
Martin Pool (mbp) said : 		#2

Bug 130617 asks for an option to automatically add during commit; we
could take that a step further and say that some users never want to
have unversioned non-ignored files in their tree, and they want to
just always add them. I might use that.

Can you help with this problem?

Provide an answer of your own, or ask Jon Loldrup for more information if necessary.

To post a message you must log in.