[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [mylyn-dev] Creating git diffs for large data sets
|
It sounds like we will need a CQ for this. If that is the case it would be best to just have a zip with the new bundles and a patch for changes to existing code.
I'm not a big fan of the process for pull requests and find it actually easies to track contributions as patches as long as we don't have Gerrit on Eclipse.org.
Steffen
On Wed, Sep 7, 2011 at 9:48 PM, Torkild Ulvøy Resheim
<torkildr@xxxxxxxxx> wrote:
Thanks David,
I eventually figured out a way. E.g. "git diff --binary refs/remotes/eclipse/master org.eclipse.mylyn.docs.epub.help > ../../Eclipse/Patches/bug_332122-help.patch". However the help plug-in by itself exceeds the limit as it contains a few images. Thank you for the pointer to the guideline. This looks like the best way to do it. I could always create a new repository using the current Mylyn base and apply the patch to it myself. Then you should get only one commit. Or maybe there is some other magic that can be applied. I don't really care about the commit history so if I loose it it's no big deal.
Best regards,
Torkild
Den 7. sep. 2011 kl. 21:41 skrev David Green:
_______________________________________________
mylyn-dev mailing list
mylyn-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mylyn-dev
--
Steffen Pingel
Committer,
http://eclipse.org/mylynSenior Developer,
http://tasktop.com