|
Size: 726
Comment: added a question
|
Size: 911
Comment: Answering the question.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 12: | Line 12: |
| * The way the changeset hash is calculated says that a changeset is a particular state of the project plus all of its ancestor states (i.e. all the changeset it took to get there). |
Changeset
A changeset (sometimes abbreviated "cset") is an atomic collection of changes to files in a repository. The act of creating a change set is usually called a ["Commit"]. The information in a changeset may include
- changes to the contents of the files
- changes to file names or other external attributes (such as execute permissions)
- information about who made the change (the "committer") and why ("comments")
A changeset is identified uniquely by a ChangeSetID. In a single repository, you can identify it using a RevisionNumber.
- Question: Is a changeset a particular state of the project (like a Subversion revision number), or is it a set of changes to files (like a Darcs patch)?
- The way the changeset hash is calculated says that a changeset is a particular state of the project plus all of its ancestor states (i.e. all the changeset it took to get there).