Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #244509
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: I've been caught out |
| Date | 2022-01-24 12:10 +0100 |
| Message-ID | <DJ5ov-4v5-13@gated-at.bofh.it> (permalink) |
| References | <DJ4sq-3Wj-3@gated-at.bofh.it> <DJ4LL-42A-1@gated-at.bofh.it> |
| Organization | only accidental |
On Monday, January 24, 2022 5:19:13 AM EST Thomas Schmitt wrote: > Hi, > > > gene@coyote:~/Debian-arm/linux$ patch -p1 ../patches/*.patch > > patch: ../patches/0001-mm-memcg-Disable-threshold-event-handlers-on- > > PREEMPT.patch: extra operand > > man patch says > > patch [options] [originalfile [patchfile]] > > With "patchfile" being singular i'd expect that it refuses if you give > more than one. > Further it does not look as if you give an "originalfile", which is > demanded by the common []-bracket around "originalfile [patchfile]". > > So what file do you want to change by the patch ? > Does ../patches/*.patch evaluate to a single file ? > No, its a directory with many patches. IMO patch should take them, in their sorted order, until its out of patches. Or do we have a gui to oversee that, something like kompare maybe? I'll take a look. > (I get that error if i give three dummy file arguments. > If i give two i get a lot of "Hunk ... FAILED at .." because my second > file is no properly formatted patch. > If i give one, the program waits for standard input.) > > > Have a nice day :) > > Thomas > Thanks Thomas, stay well now. > . Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
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