Is it possible to use Bazaar to track per-file changes as in CVS

Asked by Jeff Wepman

I am considering using Bazaar instead of CVS for our software development revision control. For our project, however, tracking changes to individual files as is done in CVS is important. Is there a reasonable way to use Bazaar so that it would emulate the behavior of CVS in having revisions apply to individual files? If so, how would I set this up? I would plan to use the client-server workflow to also emulate CVS. Any help on this would be greatly appreciated.
Thank you.

Question information

Language:
English Edit question
Status:
Solved
For:
Bazaar Edit question
Assignee:
No assignee Edit question
Solved by:
John A Meinel
Solved:
Last query:
Last reply:
Revision history for this message
John A Meinel (jameinel) said :
#1

You can always do "bzr commit filename" to only commit the changes for one
(or a few) files. Otherwise I'm not sure what you are asking.

John
=:->
On Dec 27, 2011 6:21 PM, "Jeff Wepman" <email address hidden>
wrote:

> New question #183039 on Bazaar:
> https://answers.launchpad.net/bzr/+question/183039
>
> I am considering using Bazaar instead of CVS for our software development
> revision control. For our project, however, tracking changes to individual
> files as is done in CVS is important. Is there a reasonable way to use
> Bazaar so that it would emulate the behavior of CVS in having revisions
> apply to individual files? If so, how would I set this up? I would plan to
> use the client-server workflow to also emulate CVS. Any help on this would
> be greatly appreciated.
> Thank you.
>
> --
> You received this question notification because you are an answer
> contact for Bazaar.
>

Revision history for this message
Jeff Wepman (jwepman) said :
#2

To clarify, what I really would like to do is be able to have each individual file tracked with its own revision number just like in CVS. I am not very familiar with Bazaar yet and I am not sure this is a practical way to do things in Bazaar. In order to do this would I have to make each file a branch?? The CVS model of being able to have each file tracked with its own revision number and then be able to tag a group of files at various revision levels works very well for our projects. I would like to be able to emulate this behavior in Bazaar if possible. Otherwise I believe I should just stick with CVS. Does anyone have any suggestions as to how I would do this in Bazaar?
Thank you.

Revision history for this message
Best John A Meinel (jameinel) said :
#3

You still have unique revisions of each file, just sometimes those are
shared between files. I don't know how you are using them, so I can't say
for sure, but in our experience, tree-wide identifiers are much more useful.

If you want to have $Rev$ stuff, we generally recommend against it because
of inherent issues with merging, etc. But you can use the bzr-keywords
plugin to get similar functionality for bzr.

John
=:->
On Dec 28, 2011 2:37 PM, "Jeff Wepman" <email address hidden>
wrote:

> Question #183039 on Bazaar changed:
> https://answers.launchpad.net/bzr/+question/183039
>
> Status: Answered => Open
>
> Jeff Wepman is still having a problem:
> To clarify, what I really would like to do is be able to have each
> individual file tracked with its own revision number just like in CVS. I am
> not very familiar with Bazaar yet and I am not sure this is a practical way
> to do things in Bazaar. In order to do this would I have to make each file
> a branch?? The CVS model of being able to have each file tracked with its
> own revision number and then be able to tag a group of files at various
> revision levels works very well for our projects. I would like to be able
> to emulate this behavior in Bazaar if possible. Otherwise I believe I
> should just stick with CVS. Does anyone have any suggestions as to how I
> would do this in Bazaar?
> Thank you.
>
> --
> You received this question notification because you are an answer
> contact for Bazaar.
>

Revision history for this message
Jeff Wepman (jwepman) said :
#4

Thanks John A Meinel, that solved my question.