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/NYG25YUV5J6JMXW7WMKJBRBR6G24KGBE/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "[email protected]",
    "message_id_hash": "NYG25YUV5J6JMXW7WMKJBRBR6G24KGBE",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/NYG25YUV5J6JMXW7WMKJBRBR6G24KGBE/",
    "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] Re: PacSat git repo changes",
    "date": "2023-03-03T18:59:32Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "On Fri, Mar 03, 2023 at 06:27:54PM +0000, Burns Fisher (AMSAT) via pacsat-dev wrote:\n> Hi All,\n> \n> Bill and I talked this morning and decided (actually confirmed that we both\n> agreed with what we already thought) that the PacSat git repository names\n> are confusing.  Bill and I agreed to change them, and I have done so.\n\nThanks, I was thinking about making a suggestion like this, but the new\nnames are good names.\n\n-corey\n\n> \n> This means that if you have cloned them, you will have to change the\n> upstream names in your local repository to match in order to push upstream.\n> \n> Here are the changes:\n> \n> \n> \n>    1. pacsatx is now PacSatSw  and is to be use only for software (and\n>    documentation in the form of comments).\n>    2. pacsat is now PacSatDocs and is to be used for documentation,\n>    including hardware schematics, hardware layouts etc.\n>    3. PacSatSw is now WB1FJPacSatToDelete.  This was the original repo that\n>    I created\n> \n> \n> PacSatSw can be cloned directly into Code Composer Studio--it contains some\n> of the CCS metadata to describe to the compiler where header files are etc.\n> \n> Currently there are two subdirectories in PacSatDocs:  \"requirements\" and\n> \"reference\".  Requirements contains documents about PacSat itself.\n> Reference contains files taken from other repositories, generally Fox or\n> Golf SVN.  These will usually be PDF files, and are NOT the masters.  If\n> changes are required, they must be made in the source files, which are in\n> their original repositories.\n> \n> Bill is thinking about what to do regarding hardware, but will probably add\n> a \"hardware\" folder for schematics etc etc.\n> \n> WB1FJPacSatToDelete can be deleted if no one is using it.  It has had no\n> checkins since November...it was moved to what is now PacSatSw at that time.\n> \n> We hope and expect that we will not have to do this again, and we apologize\n> to those who have to change their local git repos.  But hopefully, this\n> renaming makes it a lot more clear what is going on.\n> \n> \n> 73,\n> \n> Burns and Bill\n\n> \n> -----------------------------------------------------------\n> \n> pacsat-dev mailing list -- [email protected]\n> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]\n> To unsubscribe send an email to [email protected]\n> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org\n\n",
    "attachments": []
}