Hi Paolo,
> The hash would be different for git diff and svn diff due to the
> different headers.
The headers are not included in the hash. However, the filenames will need to
be the same - patchwork expects '-p1' patches, but normalises the top-level
directory.
For example, at http://patchwor
Hi Martin,
> > There is one header you can add to emails:
> >
> > X-Patchwork-Hint: ignore
> >
> > - this will tell patchwork to ignore the patch completely. I use this
> > when sending a "this is the stuff I'm merging for the next release"
> > email, as all of the patches have already been thro
Hi Manuel,
> > 2) Use the command-line patchwork client to update patch state when a
> > patch is committed. People have done this with a git post-commit hook to
> > update the state of the patch in patchwork; I'm not sure if svn has
> > something equivalent.
>
> Yes it does. If you tell us how t
Hi Ian,
> I can see already that to be useful for gcc today it will need some
> curating. E.g., http://patchwork.ozlabs.org/patch/54974/ is both 1)
> committed; 2) on a branch. This one
> http://patchwork.ozlabs.org/patch/54958/ is committed to trunk.
There are a number of ways to keep the patc
