)]}'
{
  "log": [
    {
      "commit": "38aa8b0c59c35d10d15ebf00ceee641f9ed7acba",
      "tree": "17444ed0f0e195677a6faaac31ba296f37b5e148",
      "parents": [
        "dc200a8848cca8b0e99012996c66f4b379a390ed"
      ],
      "author": {
        "name": "David Teigland",
        "email": "teigland@redhat.com",
        "time": "Wed Dec 13 10:37:16 2006 -0600"
      },
      "committer": {
        "name": "Steven Whitehouse",
        "email": "swhiteho@redhat.com",
        "time": "Mon Feb 05 13:35:50 2007 -0500"
      },
      "message": "[DLM] fix old rcom messages\n\nA reply to a recovery message will often be received after the relevant\nrecovery sequence has aborted and the next recovery sequence has begun.\nWe need to ignore replies to these old messages from the previous\nrecovery.  There\u0027s already a way to do this for synchronous recovery\nrequests using the rc_id number, but not for async.\n\nEach recovery sequence already has a locally unique sequence number\nassociated with it.  This patch adds a field to the rcom (recovery\nmessage) structure where this recovery sequence number can be placed,\nrc_seq.  When a node sends a reply to a recovery request, it copies the\nrc_seq number it received into rc_seq_reply.  When the first node receives\nthe reply to its recovery message, it will check whether rc_seq_reply\nmatches the current recovery sequence number, ls_recover_seq, and if not\nthen it ignores the old reply.\n\nAn old, inadequate approach to filtering out old replies (checking if the\ncurrent stage of recovery has moved back to the start) has been removed\nfrom two spots.\n\nThe protocol version number is changed to reflect the different rcom\nstructures.\n\nSigned-off-by: David Teigland \u003cteigland@redhat.com\u003e\nSigned-off-by: Steven Whitehouse \u003cswhiteho@redhat.com\u003e\n"
    },
    {
      "commit": "3bcd3687f895f178fa8480a7bcc47a363817354a",
      "tree": "13e64d5b9576b47401620aaada846f3c9c874cda",
      "parents": [
        "d35462b4bb847b68321c55e95c926aa485aecce2"
      ],
      "author": {
        "name": "David Teigland",
        "email": "teigland@redhat.com",
        "time": "Thu Feb 23 09:56:38 2006 +0000"
      },
      "committer": {
        "name": "Steven Whitehouse",
        "email": "swhiteho@redhat.com",
        "time": "Thu Feb 23 09:56:38 2006 +0000"
      },
      "message": "[DLM] Remove range locks from the DLM\n\nThis patch removes support for range locking from the DLM\n\nSigned-off-by: David Teigland \u003cteigland@redhat.com\u003e\nSigned-off-by: Steven Whitehouse \u003cswhiteho@redhat.com\u003e\n"
    },
    {
      "commit": "e7fd41792fc0ee52a05fcaac87511f118328d147",
      "tree": "eee5227088ba97daef795e385b7548d2a1cc4cb6",
      "parents": [
        "e47314207032cfd1157b8c377df162839b32ea6f"
      ],
      "author": {
        "name": "David Teigland",
        "email": "teigland@redhat.com",
        "time": "Wed Jan 18 09:30:29 2006 +0000"
      },
      "committer": {
        "name": "Steven Whitehouse",
        "email": "swhiteho@redhat.com",
        "time": "Wed Jan 18 09:30:29 2006 +0000"
      },
      "message": "[DLM] The core of the DLM for GFS2/CLVM\n\nThis is the core of the distributed lock manager which is required\nto use GFS2 as a cluster filesystem. It is also used by CLVM and\ncan be used as a standalone lock manager independantly of either\nof these two projects.\n\nIt implements VAX-style locking modes.\n\nSigned-off-by: David Teigland \u003cteigland@redhat.com\u003e\nSigned-off-by: Steve Whitehouse \u003cswhiteho@redhat.com\u003e\n"
    }
  ]
}