On Thu, Mar 1, 2012 at 9:30 AM, Leo Razoumov <[email protected]> wrote:
> On Thu, Mar 1, 2012 at 09:16, Richard Hipp <[email protected]> wrote: > > On Thu, Mar 1, 2012 at 6:18 AM, Leo Razoumov <[email protected]> > wrote: > >> > >> Brian, > >> for simplicity you might want to follow the selection rules that > >> already exist in fossil web-interface. > >> When I go to the web-interface=>Branches and select a branch I am > >> presented with a partial view of the DAG that fossil thinks is > >> relevant to the branch I chose. For the sake of consistency I would > >> prefer that limsync push/pull uses the same selection rules and > >> transfers the same commits. > > > > > > Note that there are a several of ways to view check-ins related to a > > branch. For example: > > > > http://www.fossil-scm.org/fossil/timeline?r=experimental > > http://www.fossil-scm.org/fossil/timeline?r=experimental&mionly > > http://www.fossil-scm.org/fossil/timeline?t=experimental > > > > What does "mionly" flag do? I was not able to find any documentation > for it. Look likes it has something to do with merges. > The r=BRANCH parameter normally shows merges into the branch and merges from the branch into other branches. But if you add the mionly parameter, (merge-in only) then only the merges into the branch are shown. > > --Leo-- > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
