{"thread":{"id":"32960","subject":"QNX support","startedAt":"2013-02-21T13:05:21Z","lastAt":"2013-06-26T14:36:33Z","messageCount":4,"participants":["David Ondřich","Junio C Hamano","Kraai, Matt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"209970","messageId":"430B4DD0-B796-4DB2-861D-C1F81302A4D1@aveco.com","threadId":"32960","inReplyTo":null,"subject":"QNX support","fromName":"David Ondřich","fromEmail":"david.ondrich@aveco.com","sentAt":"2013-02-21T13:05:21Z","receivedAt":"2013-02-21T13:05:21Z","isPatch":false,"sender":{"key":"david.ondrich@aveco.com","avatar":null},"body":"Hi,\n\nI've read [1] recently, there's been some QNX port being initiated. Does that involve also old versions of QNX 4?\n\nSince we are using QNX both internally and for our customers we started porting Git on QNX ourselves some time ago and we do have some experiences. Basically, it's possible to get Git up and running but there are some limitations, and some hacks have to be applied.\n\nIf some additional info wanted, please contact me.\n\ndond\n\n[1] http://lkml.indiana.edu/hypermail/linux/kernel/1302.2/00406.html"},{"id":"209983","messageId":"7vmwuxv9ou.fsf@alter.siamese.dyndns.org","threadId":"32960","inReplyTo":"430B4DD0-B796-4DB2-861D-C1F81302A4D1@aveco.com","subject":"Re: QNX support","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-02-21T17:49:37Z","receivedAt":"2013-02-21T17:49:37Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"David Ondřich\" writes:\n\njch: redirecting to the guilty party ;-)\n\n> I've read [1] recently, there's been some QNX port being\n> initiated. Does that involve also old versions of QNX 4?\n>\n> Since we are using QNX both internally and for our customers we\n> started porting Git on QNX ourselves some time ago and we do have\n> some experiences. Basically, it's possible to get Git up and\n> running but there are some limitations, and some hacks have to be\n> applied.\n>\n> If some additional info wanted, please contact me.\n"},{"id":"209984","messageId":"1B04D3EE58602B43B7D34ECC7F9E321E060FA821@SANMAIL04.corp.amo-inc.com","threadId":"32960","inReplyTo":"7vmwuxv9ou.fsf@alter.siamese.dyndns.org","subject":"RE: QNX support","fromName":"Kraai, Matt","fromEmail":"matt.kraai@amo.abbott.com","sentAt":"2013-02-21T18:04:41Z","receivedAt":"2013-02-21T18:04:41Z","isPatch":false,"sender":{"key":"kraai@ftbfs.org","avatar":null},"body":"Junio C Hamano writes:\n> \"David Ondřich\" writes:\n> > I've read [1] recently, there's been some QNX port being\n> > initiated. Does that involve also old versions of QNX 4?\n\nNo, I haven't been working on QNX 4 support. I've been targeting QNX 6.3.2, with a little testing on QNX 6.5.0. I doubt what I've done would work on QNX 4 since it's so different from QNX 6.\n \n> > Since we are using QNX both internally and for our customers we\n> > started porting Git on QNX ourselves some time ago and we do have\n> > some experiences. Basically, it's possible to get Git up and\n> > running but there are some limitations, and some hacks have to be\n> > applied.\n> >\n> > If some additional info wanted, please contact me.\n\nNow that Git is building and usable, the next logical step is to investigate and fix the test suite failures. If you have any information about these, that could be helpful.\n\n-- \nMatt\n"},{"id":"222020","messageId":"7213649B-3168-4089-8592-B8FDE2F2F705@aveco.com","threadId":"32960","inReplyTo":"1B04D3EE58602B43B7D34ECC7F9E321E060FA821@SANMAIL04.corp.amo-inc.com","subject":"Re: QNX support","fromName":"David Ondřich","fromEmail":"david.ondrich@aveco.com","sentAt":"2013-06-26T14:36:33Z","receivedAt":"2013-06-26T14:36:33Z","isPatch":false,"sender":{"key":"david.ondrich@aveco.com","avatar":null},"body":"Hi,\n\nsorry for long delay, I was busy on some important project so far. However, we’ve found out really bad thing recently.\n\nOn Feb 21, 2013, at 7:04 PM, \"Kraai, Matt\" wrote:\n> Junio C Hamano writes:\n>> \"David Ondřich\" writes:\n>>> I've read [1] recently, there's been some QNX port being\n>>> initiated. Does that involve also old versions of QNX 4?\n> \n> No, I haven't been working on QNX 4 support. I've been targeting QNX 6.3.2, with a little testing on QNX 6.5.0. I doubt what I've done would work on QNX 4 since it's so different from QNX 6.\n\nIt certainly wouldn't work, since there’s limitation to 48 characters for filename in filesystem – it can be beaten up by changes in git index / pack / keep mechanism but it requires on-the-fly transformation when replicating a repository from / to other place. I've thought we would be able to implement such translation but what came up was its cost would be too high. It is definitely doable but for us it's currently the showstopper.\n\ndond"}]}