Huh, the "fossil json tags list" output seems inconsistent with these other two:

{
    "fossil":"aa55cf3aa6d4c74c781c1c8d2f9b0807c3a2740c",
    "timestamp":1330464343,
    "command":"tag/list",
    "procTimeMs":1,
    "payload":{
        "raw":false,
        "includeTickets":false,
        "tags":[
            "branch",
            "closed",
            "cluster",
            "comment",
            "date",
            "event-2bc72955fd5f251cf783d3729b1fb9e84fc7138b",
            "event-66cb21a5ab54ee8598b681bf98aafabc1ba4ec87",
            "event-7f1513705b86e8e7292b83078b22e04bf333cdd4",
            "event-c0395a4f0df7991135418b51a510c39e43508cf4",
            "event-df0658580af71cbfc4e63926ad747187f13bef43",
            "event-f37029d1ca46c9d9d9b5afbc9a778b05a0f54a00",
            "0.8",
            "0.9.0rc1",
            "0.9.0rc2",
            "1.0.0",
            "1.0.1",
            "1.1.0",
            "1.1.1",
            "1.1.2",
            "1.1.3",
            "master",
            "release",
            "review",
            "scripting",
            "trunk",
            "wiki-Spiel",
            "wiki-download",
            "wiki-faq",
            "wiki-features",
            "wiki-release-notes-template",
            "wiki-source"
        ]
    }
}

In particular, it lists wiki pages and events. I'm not sure how those qualify as tags, unless tags are how URLs are resolved to artifacts, but those tags aren't reported either via the web or command line interfaces. Not being critical, I'm just genuinely confused, and think this is why consistency would be useful. If a tag is visible in all interfaces, we should be able to say "that's because it's a non-propagating third degree black belt ninja tag" or something. Seriously, tags are confusing when you get beyond the basics.


On 02/28/2012 03:19 PM, Stephan Beal wrote:
On Tue, Feb 28, 2012 at 9:40 PM, Nolan Darilek <[email protected] <mailto:[email protected]>> wrote:

    I'm wondering if what I get with "fossil tag list" might be
    brought in sync with what I get from the web interface, since that
    is a more useful list of tags for my project?


FWIW: the JSON API's tags interface offers all or most of the options supported by the HTML interface. That said, i personally find it difficult to remember all the different options and the ways they interact (and change the response structure), and the current interface is open to suggestions and up for debate:

https://docs.google.com/document/d/1fXViveNhDbiXgCuE7QDXQOKeFzf2qNUkBEgiUvoqFN4/edit?pli=1#heading=h.h1ag4m728xv5

i'd especially like to hear from those who make heavy use of tags (i don't).

stephan@tiny:~/cvs/fossil/fossil$ f json tag
{
"fossil":"affb0019c9068467a6fe7cfbc76d0ca233721be3",
"timestamp":1330463892,
"resultCode":"FOSSIL-3002",
"resultText":"No subcommand specified. Try one of (add, cancel, find, list).",
"command":"tag",
"procTimeMs":4
}


--
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal



_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to