partial commits

Greg Ward greg-hg at gerg.ca
Fri Aug 7 11:19:34 CDT 2009


On Thu, Aug 6, 2009 at 5:51 PM, Edward Peschko<horos11 at gmail.com> wrote:
> That has to do with partial commits. Say I modify 3 files - totally
> unrelated changes, they so happen to work with each other but I want
> to track them separately, and then I get 1 file working (and want to
> commit and push it).
>
> As it stands, there is no easy way to do this. I can modify that one
> file, and commit it, but as it stands there is no good way to push it
> - that I can see - without committing the other two files. I can pull,
> and update, but when I try to push it says:
>
>    - abort: push creates new remote branches! (did you forget to
> merge? use push -f to force)

This makes no sense.  If push gives you this message, it most likely
means someone (possibly you) has pushed changes from another
repository.  Can you give an example sequence of commands that
reproduces the problem you have described?  That is, modify 3 files,
commit 1, push, push rejected?  Mercurial should not behave like that.

Also, it would be helpful to know which version you're using.

Greg



More information about the Mercurial mailing list