# Re: Re :Re: [PATCHv3 0/1] git-p4 unshelve

1 messages from 2018-06-18 to 2018-06-18. Participants: Luke Diamand.
Thread: https://gitlist.dev/t/48729

## Luke Diamand, 2018-06-18 11:30

Subject: Re: Re :Re: [PATCHv3 0/1] git-p4 unshelve
Message-ID: <CAE5ih78DG1o2eKSNSbdJ4AeYLpAWVowp7NqhrobkxAdQ8ZTNdA@mail.gmail.com>
URL: https://gitlist.dev/e/CAE5ih78DG1o2eKSNSbdJ4AeYLpAWVowp7NqhrobkxAdQ8ZTNdA%40mail.gmail.com

```
On 16 June 2018 at 10:58, merlorom@yahoo.fr <merlorom@yahoo.fr> wrote:
> Yes Luke, my colleagues and I, we care ! Our repository is p4 (choice of the
> high management, sigh...). Some of us are working natively on p4, but others
> like me are working on git through git-p4. We often want to share pieces of
> codes to check compilation on misc platforms/configs, and shelve/unshelve
> mechanism is commonly used between nativ p4 users.
> For git-p4 users we have a temporary hack to unshelve, but it often fails to
> apply the whole p4 diff, and we end up finishing stuff by hand, checking
> line by line, sigh... Without speaking about diffs that are accross several
> local workspaces.
> Hopefully it is on small shelved p4 change lists for the moment, but we
> cannot deploy on a larger scale.
> Please continue your hard work on unshelve stuff.
>
> For your last remark, the members of our team often need to work on non
> synchro revisions, but still need to share via shelve/unshelve, and I am
> sure we will have conflits as you describe, leading unshelve to fail.
> Automatic fast import would save us the need to stop our current work, sync
> with p4 and launch a 1h compilation, before we could unshelve... So yes we
> need it !

OK, I'll give it a go, in my copious free time :-)

Luke

```