Hi Harry, > added 2 changesets with 0 changes to 1 files > > Now that's a nice and very clear message "2 changesets with 0 changes to 1 > files". > The logic of that is really enlightening. :-)
I think, I'm responsible at least partially for this. I added a tag for the release candidate. This changes a mercurial internal file, which does not belong to a specific branch (or it belongs to default, I'm not so sure). > Now I do a "hg merge" and a 'hg commit -m "merged changes committed"' > followed by the "push....." > > Now it mentions: > remote: adding changesets > remote: adding manifests > remote: adding file changes > remote: added 4 changesets with 5 changes to 6 files > remote: Running changegroup hook > remote: notify: sending 1 subscribers 1 changes > remote: notify: sending 1 subscribers 1 changes > remote: notify: sending 1 subscribers 1 changes > remote: notify: sending 1 subscribers 1 changes > > Does it now send a mail to the last 4 committers/pushers? No, it sends one mail per changeset to the hugin-cvs mailing list. >Does it/Wants it > to update their local copies next time they pull? And why then if a hg pull > always does that? Do they now have to merge as well? Also due to my > actions/mistakes? No, others have not to merge. > > I assume it is now OK? (please?, yes?) Yes, it's ok on my side. Thomas -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
