Mercurial copy patch to repository?

Hg import should be able to handle git-style patches. Use hg import --no-commit if you don't want it to automatically commit the changes after each patch is imported. Mozilla's FAQ mentions this: https://developer.mozilla.Org/en/Mercurial_FAQ#How_can_I_diff_and_patch_files.3f.

That's the only trust model mercurial has built-into it, and it won't prevent the applying of patches. – Ry4an Apr 13 '10 at 4:17 I am fairly new to this but here is the error message patching file plugins/supported/text_editor/commands/editing. Js Hunk #1 FAILED at 129 1 out of 1 hunks FAILED -- saving rejects to file plugins/supported/text_editor/commands/editing.js.

Rej abort: patch failed to apply – Abid Apr 13 '10 at 4:19.

Try hg import --no-commit, Mozilla has a rather useful FAQ regarding trading patches between Git and Mercurial. Depending on your platform, you can also just use patch, e.g. Patch -p1 That may actually be better as you'll see any fuzz and not have to deal with trusting the author just for one patch. Edit If your patch does not go in cleanly, none of the above methods are going to work.

Your code base is not what the patch expects if hunks fail to apply. Look at the rejects and see what the patch expected your code to be at any given line, then rebase accordingly.

Does not work Triedit – Abid Apr 13 '10 at 4:50 I think hg importing a patch is better, as it will preserve the original committer’s name and timestamp. – Laurens Holst Apr 13 '10 at 18:56.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.