Email Detail

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/L3UX33VSSHIGKFLTBXYN7LCOD5YFT3AJ/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "L3UX33VSSHIGKFLTBXYN7LCOD5YFT3AJ",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/L3UX33VSSHIGKFLTBXYN7LCOD5YFT3AJ/",
    "sender": {
        "address": "minyard (a) acm.org",
        "mailman_id": "59a713764a2e4ccabdcfd85f5b213a94",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/59a713764a2e4ccabdcfd85f5b213a94/emails/"
    },
    "sender_name": "Corey Minyard",
    "subject": "[pacsat-dev] Filesystem interface to mram",
    "date": "2023-04-04T13:39:52Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "I have integrated the Reliance Edge filesystem into the PacSatSw\nrepository in the \"filesystem\" branch.  However, it is still missing the\nlower level interface to the mram devices.\n\nAre we using the mram code in the deviceSupport directory?  If so, the\nread and write operations (readMRAMWord, writeMRAMWord) don't have\nprototypes in the header.  But I can fix that and integrate.\n\nJonathan, I guess I'll need a launchpad and a board with the mram, since\nthe qemu stuff didn't work out.\n\n-corey\n",
    "attachments": []
}