This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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://patchwork.ozlabs.org/patch/55140/
--- gcc/config/rs6000/e500.h (revision 160245) +++ gcc/config/rs6000/e500.h (working copy)
The parser normalises this to:
--- a/config/rs6000/e500.h +++ b/config/rs6000/e500.h
which may or may not be what you want here (svn outputs -p0?).
--- configure (revision blah) +++ configure (working copy)
The only difficulty is that the parser does not specify an order for the files in a patch; I believe git orders the file changes alphabetically by filename, but svn does not. This may cause different hashes.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |