On Sat, Jan 19, 2013 at 02:01:56PM +0200, John Found wrote: > As long as the merge command works on the current checkout, you can do any > number of merges and then make a "commit". The result should be something > similar. >
But why would someone merge the leave, the previous commit, and also its previous commit? Maybe because of a merge without committing, once trunk gets a new checkin, merge again, then again the same, until at the end you commit? I quite don't get why would someone do that, though :) > On Fri, 18 Jan 2013 17:48:59 +0100 > Lluís Batlle i Rossell <vi...@viric.name> wrote: > > > Hello, > > > > looking at the tcl timeline, I've just seen a checkin like this: > > http://core.tcl.tk/tcl/timeline?f=3c4edc83aae0e671 > > > > What is that kind of usage? I feel strange that the "merge trunk" has arrows > > from *3 trunk leaves*, and *2 more checkins* from one of the trunk branches. > > > > What have they typed to achieve that merge? Why do they have multiple > > 'trunk'? > > > > I've no idea of how tcl development works, but I'd like to know what fossil > > usage pattern they use. > > > > Regards, > > Lluís. > > _______________________________________________ > > fossil-users mailing list > > fossil-users@lists.fossil-scm.org > > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > > -- > John Found > http://asm32.hopto.org > _______________________________________________ > 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
