A solution to this is to use `git phab attach -n $patches`. The -n option
makes the patches independent of other patches, so they do not get added to
any stack.
Here are some example workflows which avoid making large stacks of
unrelated patches:
* Have series of 3 patches, 2 independent patches,
‐‐‐ Original Message ‐‐‐
On Thursday, January 17, 2019 2:31 AM, Xavi Artigas
wrote:
> Just so you all know (I am looking at nobody in particular).
<3
> When you submit a long stack of unrelated patches to Phab, to test if a
> single patch works I need to apply all the previous ones, O
On Thu, Jan 17, 2019 at 7:32 PM Xavi Artigas wrote:
>
> Just so you all know (I am looking at nobody in particular).
>
> When you submit a long stack of unrelated patches to Phab, to test if a
> single patch works I need to apply all the previous ones, OR I need to
> apply the dependencies one by
Just so you all know (I am looking at nobody in particular).
When you submit a long stack of unrelated patches to Phab, to test if a
single patch works I need to apply all the previous ones, OR I need to
apply the dependencies one by one, but then I need to find out which
patches in the stack are
