{"thread":{"id":"48729","subject":"Re: Re :Re: [PATCHv3 0/1] git-p4 unshelve","startedAt":"2018-06-18T11:30:57Z","lastAt":"2018-06-18T11:30:57Z","messageCount":1,"participants":["Luke Diamand"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"350377","messageId":"CAE5ih78DG1o2eKSNSbdJ4AeYLpAWVowp7NqhrobkxAdQ8ZTNdA@mail.gmail.com","threadId":"48729","inReplyTo":null,"subject":"Re: Re :Re: [PATCHv3 0/1] git-p4 unshelve","fromName":"Luke Diamand","fromEmail":"luke@diamand.org","sentAt":"2018-06-18T11:30:53Z","receivedAt":"2018-06-18T11:30:57Z","isPatch":false,"sender":{"key":"luke@diamand.org","avatar":"https://avatars.githubusercontent.com/u/5330967?v=4"},"body":"On 16 June 2018 at 10:58, merlorom@yahoo.fr <merlorom@yahoo.fr> wrote:\n> Yes Luke, my colleagues and I, we care ! Our repository is p4 (choice of the\n> high management, sigh...). Some of us are working natively on p4, but others\n> like me are working on git through git-p4. We often want to share pieces of\n> codes to check compilation on misc platforms/configs, and shelve/unshelve\n> mechanism is commonly used between nativ p4 users.\n> For git-p4 users we have a temporary hack to unshelve, but it often fails to\n> apply the whole p4 diff, and we end up finishing stuff by hand, checking\n> line by line, sigh... Without speaking about diffs that are accross several\n> local workspaces.\n> Hopefully it is on small shelved p4 change lists for the moment, but we\n> cannot deploy on a larger scale.\n> Please continue your hard work on unshelve stuff.\n>\n> For your last remark, the members of our team often need to work on non\n> synchro revisions, but still need to share via shelve/unshelve, and I am\n> sure we will have conflits as you describe, leading unshelve to fail.\n> Automatic fast import would save us the need to stop our current work, sync\n> with p4 and launch a 1h compilation, before we could unshelve... So yes we\n> need it !\n\nOK, I'll give it a go, in my copious free time :-)\n\nLuke\n"}]}