All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: I have a large patch in the 2000 lines. What to do?
Date: Fri, 16 Oct 2015 14:31:10 -0700	[thread overview]
Message-ID: <20151016213110.GA23593@kroah.com> (raw)
In-Reply-To: <CAENf94LAfnJaDDUv9k8By-yTC4kSyw-2iHb+QMDfkdGz3qwAWw@mail.gmail.com>



On Fri, Oct 16, 2015 at 06:14:01PM -0300, Julio Faracco wrote:
> 
> What is the recommendation when I change a structure in a include file
> and this change causes a lots of new changes, for example?

You do the change in a way that does not cause build failures and spread
the patches out over all subsystems to fix things up.

Do you have a specific example you were thinking of so that I can show
how it can be done in this way?

thanks,

greg k-h

      reply	other threads:[~2015-10-16 21:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09 18:45 I have a large patch in the 2000 lines. What to do? Ivan Safonov
2015-10-09 19:12 ` Anish Kumar
2015-10-09 19:20   ` Greg KH
2015-10-10  1:02     ` Ivan Safonov
2015-10-10 14:14       ` Greg KH
2015-10-16 21:14         ` Julio Faracco
2015-10-16 21:31           ` Greg KH [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151016213110.GA23593@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.