Hi,
If you want to push changesets which you considered 'complete', I also
recommend you give the 'task' extension a try:
http://www.selenic.com/mercurial/wiki/index.cgi/TasksExtensionThis extension not only provides the functions which similar to
bookmarks, but also has built-in stash which could automatically save
your current changes in working directory (yes, just like git stash).
Sincerely yours,
Willie
On Fri, Apr 10, 2009 at 7:24 PM, amaslov <
amaslov.p@...> wrote:
>
> Hello,
>
> I have been using local branches in git, maybe this breaks my attempts to
> master hg bookmarks...
>
> With Mercurial 1.2.1 I do the following:
> 1) create a repository (let's call it "repo1"), add a file "file1.txt"
> there, commit it
> 2) clone the repository (let's call this one "repo2"), add bookmarks
> extension and "track.current = True" under "[bookmarks]" to hgrc, create
> bookmarks "master" and "quickfix" there
> 3) at repo2: "hg up -C quickfix", change the file "file1.txt", commit it
> 4) at repo2: switch to master: "hg up -C master", hg out - and see that the
> changes to "file1.txt" are propagated into push.
>
> I expected that only changes to the branch I am on are propagated into
> push. Is it an expected behavior?
>
> I am not very proficient with Mercurial and sorry for any stupidity I have
> written.
>
> Thanks a lot for help!
>
> Regards,
> Alexey
> --
> View this message in context:
http://www.nabble.com/Please-help-with-Mercurial-Bookmarks-workflow-tp22986564p22986564.html> Sent from the Mercurial mailing list archive at Nabble.com.
>
> _______________________________________________
> Mercurial mailing list
>
Mercurial@...
>
http://selenic.com/mailman/listinfo/mercurial>
_______________________________________________
Mercurial mailing list
Mercurial@...
http://selenic.com/mailman/listinfo/mercurial
