reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Shebordaev <vladimir.shebordaev@gmail.com>
To: doiggl@velocitynet.com.au
Cc: reiserfs-devel@vger.kernel.org, Ivan Shapovalov <intelfx100@gmail.com>
Subject: Re: Bundling patches together.
Date: Sat, 21 Feb 2015 10:27:24 +0300	[thread overview]
Message-ID: <1424503644.27942.14.camel@home.ted.local> (raw)
In-Reply-To: <a93e264428ba5eaa329137f88ff880c6@mail.velocitynet.com.au>

Well, the task to make RPM apply as many patches as you want is almost
trivial. 

I'm not quite sure about OpenSUSE spec files, but as to RedHat/Fedora
ones you have to

1) enumerate the patches using Patch[0-99999] declarations, 
2) apply patches in sequence using corresponding 
%patch[0-99999] directive in %prep section.

Please notice it is completely up to you to maintain proper patch
numbering and application sequence. I am not quite sure about maximal
patch number that RPM accepts, but at least 5-digit values are usually
fine.

Adding tens lines of text to spec file is evidently less complicated
task than merging hundreds lines of working kernel code. The last one is
not also that complicated but is rather useless, dull and error-prone
procedure. 

Once you correctly add those 20 lines to your spec file, you will be
able to build the package as many times as you want with no risk to miss
a part of the patch at all.

In the hope it helps.

--
Regards,
Vladimir

On Sat, 2015-02-21 at 16:59 +1100, doiggl@velocitynet.com.au wrote:
> Hello Ivan,
> Can you provide a single patch for [1] when it accepted into Reiser4.
> 
> [1]
> [PATCHv5 00/10] reiser4: batch discard support (FITRIM ioctl): initial
> implementation
> 
> Reaon for asking:
> Easier to apply one patch rather than ten and minimises risk of missing a
> part of the patch.
> 
> --Thanks Glenn
> --
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  reply	other threads:[~2015-02-21  7:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-21  5:59 Bundling patches together doiggl
2015-02-21  7:27 ` Vladimir Shebordaev [this message]
2015-02-21 10:12 ` Ivan Shapovalov

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=1424503644.27942.14.camel@home.ted.local \
    --to=vladimir.shebordaev@gmail.com \
    --cc=doiggl@velocitynet.com.au \
    --cc=intelfx100@gmail.com \
    --cc=reiserfs-devel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).