* Bundling patches together.
@ 2015-02-21 5:59 doiggl
2015-02-21 7:27 ` Vladimir Shebordaev
2015-02-21 10:12 ` Ivan Shapovalov
0 siblings, 2 replies; 3+ messages in thread
From: doiggl @ 2015-02-21 5:59 UTC (permalink / raw)
To: reiserfs-devel; +Cc: Ivan Shapovalov
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Bundling patches together.
2015-02-21 5:59 Bundling patches together doiggl
@ 2015-02-21 7:27 ` Vladimir Shebordaev
2015-02-21 10:12 ` Ivan Shapovalov
1 sibling, 0 replies; 3+ messages in thread
From: Vladimir Shebordaev @ 2015-02-21 7:27 UTC (permalink / raw)
To: doiggl; +Cc: reiserfs-devel, Ivan Shapovalov
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Bundling patches together.
2015-02-21 5:59 Bundling patches together doiggl
2015-02-21 7:27 ` Vladimir Shebordaev
@ 2015-02-21 10:12 ` Ivan Shapovalov
1 sibling, 0 replies; 3+ messages in thread
From: Ivan Shapovalov @ 2015-02-21 10:12 UTC (permalink / raw)
To: doiggl; +Cc: reiserfs-devel
[-- Attachment #1: Type: text/plain, Size: 744 bytes --]
On 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.
Hi Glenn,
let me say this again: if/when any patches are reviewed and added into
reiser4, they will be merged with the main patch. So if you are just
building kernels, you do not need to worry about any other patches
floating around the mailing list. Just grab what you see from the
project page at sourceforge.
HTHs,
--
Ivan Shapovalov / intelfx /
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 213 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-02-21 10:12 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-02-21 5:59 Bundling patches together doiggl
2015-02-21 7:27 ` Vladimir Shebordaev
2015-02-21 10:12 ` Ivan Shapovalov
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).