[Mesa-dev] Large patch advice

[Jason Ekstrand]

On Fri, Jun 8, 2018 at 9:49 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote:

> Push it to a branch somewhere, and mail the commit description + link
> to patch. No need to stick 3.1MB of data into everyone's inboxes.
>

That's a good plan.  Another thing you could do would be to run git
format-patch with some of the options for ignoring whitespace and see if
that's sendable.  Obviously, if it's a major refactor, that's not what
you'll merge but it might make it easier to verify that nothing actually
changed.  Also, if you used a tool or script to do the refactoring, it
might be good to put in the e-mail what you did.  Just some thoughts that
you can take or leave at-will. :-)

--Jason



> On Fri, Jun 8, 2018 at 12:40 PM, Hota, Alok <alok.hota at intel.com> wrote:
> > Hi all,
> >
> > I have a patch that I would like to send in, but it’s quite large. We
> had a
> > code formatting overhaul for the SWR gallium driver, and the resulting
> patch
> > file is 3.1 MB. Will this go through the mailing system okay? If not,
> what’s
> > the best course of action to submit this patch to mesa-dev?
> >
> > -Alok
> >
> >
> >
> >
> > _______________________________________________
> > mesa-dev mailing list
> > mesa-dev at lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/mesa-dev
> >
> _______________________________________________
> mesa-dev mailing list
> mesa-dev at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/mesa-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20180608/29b0b4a4/attachment.html>