On Wed, Feb 29, 2012 at 9:23 PM, Brian Smith <br...@linuxfood.net> wrote:
> I think the only appropriate response is "Oh snap". > Indeed! How does this look: stephan@tiny:~/cvs/fossil/fossil/src$ f json timeline ci -n 1 -I 2 { ... "payload":{ "limit":1, "timeline":[{ "type":"checkin", "uuid":"ef561ed0a56a45a23ebf4f1cef6abbed8c98d38d", ... "parentUuid":"affb0019c9068467a6fe7cfbc76d0ca233721be3", "parents":["affb0019c9068467a6fe7cfbc76d0ca233721be3"], "tags":["trunk"] }] } } With parentUuid now explicitly refering to the "primary parent" (i admit that i have little idea what that really means). Incidentally, the "parents" array puts the primary parent first, with the remaining elements in unspecified order, so we could just as well drop "parentUuid" altogether. :-? > > > Would it be worth while to change "parentUuid" to "parents" for the sake > of consistency with the "tags" attribute? > > > Absolutely. i'll try to get to that this weekend. i had never considered > multiple parents (and i'm not sure _which_ parent is selected right now - > the first, last, or unspecified!). > > Thanks, Brian! > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > http://gplus.to/sgbeal > > _______________________________________________ > 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 > > -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users