Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #244587

Re: I've been caught out

From <tomas@tuxteam.de>
Newsgroups linux.debian.user
Subject Re: I've been caught out
Date 2022-01-25 14:10 +0100
Message-ID <DJtKa-2BU-7@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> <DJtqN-2dP-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Tue, Jan 25, 2022 at 01:33:45PM +0100, Vincent Lefevre wrote:
> On 2022-01-25 09:12:52 +0100, Urs Thuermann wrote:
> > Greg Wooledge <greg@wooledge.org> writes:

[...]

> > 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

But exactly that was the original poster's problem. With his shell (most
probably bash) this leads to an "ambiguous redirect". Your zsh does an
implicit cat when it sees multiple files.

> > 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.

Yes, this is an independent issue. The OP's patches (at least one of
them, but we do induction :) are prepended by leading-zero four-digit
numbers, so assuming they are intended to be ordered by that seems low
risk ;-)

Cheers
-- 
t

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


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