I've been following fossil community just a couple of weeks ago and you guys rocks! I really appreciate all your answers and the "welcome" I've received...
Thanks once more for this amazing project Erlis On Fri, Sep 30, 2011 at 8:04 PM, Stephan Beal <sgb...@googlemail.com> wrote: > On Fri, Sep 30, 2011 at 10:38 PM, Erlis Vidal <er...@erlisvidal.com>wrote: > >> My mistake was that I create a branch but forgot to check it out, and did >> a couple of commits. Then I realized that the branch was there, but empty... >> it was my bad. >> > > In such a case you can use: > > fossil commit -m '...' --branch branchname ...file list... > > to commit the changes to a specific branch. i _think_ that will work with > existing branches, but it might require a _new_ branch name. > > I just noticed in the timeline that with fossil, creating a branch creates >> also a commit... hmmm now I see something different... >> > > LOL. There was a long debate about that behaviour a couple months back. > Some prefer it that way, some prefer to commit to a specific branch to start > the branch. > > Is there something I can read that could explain me better the "fossil >> internals" a wiki? >> > > All of those docs are over on the fossil web site. Try: > > http://fossil-scm.org/index.html/doc/trunk/www/permutedindex.wiki > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
