Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #244584
| From | Vincent Lefevre <vincent@vinc17.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: I've been caught out |
| Date | 2022-01-25 13:50 +0100 |
| Message-ID | <DJtqN-2dP-1@gated-at.bofh.it> (permalink) |
| References | <DJ4sq-3Wj-3@gated-at.bofh.it> <DJ6Xf-5h8-9@gated-at.bofh.it> <DJpdv-86Y-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 2022-01-25 09:12:52 +0100, Urs Thuermann wrote: > Greg Wooledge <greg@wooledge.org> writes: > > On Mon, Jan 24, 2022 at 05:01:21AM -0500, gene heskett wrote: > > > gene@coyote:~/Debian-arm/linux$ patch -p1 ../patches/*.patch > > > > That's not how you do it. patch(1) can only accept one patch at a time, > > and it expects to see it on standard input. > > > > for p in ../patches/*.patch; do patch -p1 < "$p"; done > > You can even do the somewhat easier > > cat ../patches/*.patch | patch -p1 > > which will do the same. Even easier (works with zsh, multios enabled, which is the default): patch -p1 < ../patches/*.patch > However, often the order of patches is important when some patch > depends on another being applied before. Then *.patch will probably > not work since it applies patches in alphabetical order. Sometimes patch names are prepended with a number with a fixed number of digits (e.g., 3) to make sure that this works. -- Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
I've been caught out gene heskett <gheskett@shentel.net> - 2022-01-24 11:10 +0100
Re: I've been caught out "Thomas Schmitt" <scdbackup@gmx.net> - 2022-01-24 11:30 +0100
Re: I've been caught out gene heskett <gheskett@shentel.net> - 2022-01-24 12:10 +0100
Re: I've been caught out <tomas@tuxteam.de> - 2022-01-24 12:20 +0100
Re: I've been caught out gene heskett <gheskett@shentel.net> - 2022-01-24 21:40 +0100
Re: I've been caught out "Thomas Schmitt" <scdbackup@gmx.net> - 2022-01-24 12:40 +0100
Re: I've been caught out Mark Allums <mark@allums.email> - 2022-01-24 13:20 +0100
Re: I've been caught out <tomas@tuxteam.de> - 2022-01-24 11:30 +0100
Re: I've been caught out <tomas@tuxteam.de> - 2022-01-24 21:40 +0100
Re: I've been caught out gene heskett <gheskett@shentel.net> - 2022-01-24 21:40 +0100
Re: I've been caught out Greg Wooledge <greg@wooledge.org> - 2022-01-24 13:50 +0100
Re: I've been caught out Urs Thuermann <urs@isnogud.escape.de> - 2022-01-25 09:20 +0100
Re: I've been caught out Vincent Lefevre <vincent@vinc17.net> - 2022-01-25 13:50 +0100
Re: I've been caught out <tomas@tuxteam.de> - 2022-01-25 14:10 +0100
Re: I've been caught out Greg Wooledge <greg@wooledge.org> - 2022-01-25 13:50 +0100
Re: I've been caught out gene heskett <gheskett@shentel.net> - 2022-01-25 18:00 +0100
csiph-web