Sergei Steshenko wrote:
> Greg Wooledge wrote:
> > And the only way you'll know that is by reading the patch itself.
>
> No, there shouldn't be
But so it is just the same. Patches may be created in different ways
and that causes the recorded paths to either have no leading
directories, one leadin
--- On Thu, 11/19/09, Greg Wooledge wrote:
> From: Greg Wooledge
> Subject: Re: bash40-011 patch can't be applied cleanly
> To: "Sergei Steshenko"
> Cc: bug-bash@gnu.org
> Date: Thursday, November 19, 2009, 5:05 AM
> On Wed, Nov 18, 2009 at 06:54:01PM
> -
On Wed, Nov 18, 2009 at 06:54:01PM -0800, Sergei Steshenko wrote:
> My script was applying patches from 'bash-4.0-patches' directory, not from
> 'bash-4.0' one, and maybe this was my mistake.
Yes. You should always be in the source directory you're patching,
when you apply a patch. The only ques
--- On Wed, 11/18/09, Chet Ramey wrote:
> From: Chet Ramey
> Subject: Re: bash40-011 patch can't be applied cleanly
> To: "Sergei Steshenko"
> Cc: bug-bash@gnu.org, chet.ra...@case.edu
> Date: Wednesday, November 18, 2009, 6:35 PM
> Sergei Steshenko wrot
Sergei Steshenko wrote:
> As one can see, patches before the one in question were cleanly applied.
>
> Could you please fix it ?
$ cd bash-4.0
$ for f in {01..35}; do echo bash40-0$f: ; patch -p0 <
../bash-4.0-patches/bash40-0$f; done
bash40-001:
patching file parse.y
patching file patchlevel.h
--- On Wed, 11/18/09, Sergei Steshenko wrote:
> From: Sergei Steshenko
> Subject: bash40-011 patch can't be applied cleanly
> To: bug-bash@gnu.org
> Date: Wednesday, November 18, 2009, 5:43 PM
> Hello,
>
> here is screen output of patches application proces
Hello,
here is screen output of patches application process:
"
build.pl :INFO: executing ==> cd
/mnt/sdb8/sergei/AFSWD_debug/build/bash-4.0/../bash-4.0-patches; \patch -p0 <
bash40-001
patching file ../bash-4.0/parse.y
patching file ../bash-4.0/patchlevel.h
build.pl :INFO: executing ==> cd
/mn
