Masatake YAMATO <[EMAIL PROTECTED]> writes: > However, in another project, an user may want to send a patchset(changeset?) > to > a project.
The recommended way to do so is to publish your archive and to send a merge request (not star-merge, but replay or equivalent. See the cherrypicking chapter in the tutorial). However, sending the changeset (as a .tar.gz file by email for example) is also a possibility. > get-changeset : retrieve a changeset from an archive Very efficient command. Just get the changeset from the archive and copy it to your local tree. (you could do the same with 'cp' or 'wget') That's the command to use if your patch consists only of one changeset (one revision) in the archive. > changes : report about local changes in a project tree Local changes only. This is a kind of "private" information. If you want to make it public, commit first. In particular, the changeset will not contain new patch-log entries, so, applying it to another tree will not keep the history of patches applied to your project. > changeset : compute a whole-tree changeset I think this is mainly the low-level command used by tla changes > * Commands for Branching and Merging > > delta : Compute a changeset (or diff) between any > two trees or revisions This is the right command in your case I think. > Of course there is one more question. > When I received a patchset, Which command should I use to apply the patchset > to my tree? tla apply-changeset should do it. -- Matthieu
