Re: DJGPP support for bison

[Tim Van Holder]

On Wed, 2002-02-13 at 14:55, Juan Manuel Guerrero wrote:
> On 11 Feb 2002 14:38:34 +0100, Akim Demaille wrote:
> > Juan> savannah id : juan_g
> >
> > Done, please, proceed.  I'd appreciate if you could also update the
> > NEWS file.  Pay attention to work on the BRANCH_1-30 or so (I don't
> > remember its exact name).
> 
> Please, can someone tell me which is the appropiate branch to commit
> my patch?
> Please note that I am new to cvs.
> I have checked out BISON-1_33 branch to create the patch below using
> cvs command: co -r BISON-1_33 bison. Now I get the following errors:

Try using 'cvs status -v' on some file (e.g. ChangeLog).
This will list all available tags & branches, like so:

   Existing Tags:
        BISON-1_33                      (revision: 1.173.2.276)
        before-m4-back-end              (revision: 1.532)
        BISON-1_32                      (revision: 1.173.2.270)
        BISON-1_31                      (revision: 1.173.2.262)
        BISON-1_30l                     (revision: 1.173.2.260)
        BISON-1_30k                     (revision: 1.173.2.258)
        BISON-1_30j                     (revision: 1.173.2.256)
        BISON-1_30i                     (revision: 1.173.2.243)
        BISON-1_30h                     (revision: 1.173.2.235)
        BISON-1_30g                     (revision: 1.173.2.229)
        BISON-1_30f                     (revision: 1.173.2.223)
        BISON-1_30e                     (revision: 1.173.2.161)
        BISON-1_30d                     (revision: 1.173.2.147)
        BISON-1_30c                     (revision: 1.173.2.114)
        BISON-1_30b                     (revision: 1.173.2.107)
        BISON-1_30a                     (revision: 1.173.2.93)
        BISON-1_30                      (revision: 1.173.2.81)
        BISON-1_29f                     (revision: 1.173.2.79)
        BISON-1_29e                     (revision: 1.173.2.78)
        BISON-1_29d                     (revision: 1.173.2.74)
        after-merge-branch-1_29         (revision: 1.223)
        pre-merge-of-1-29-branch        (revision: 1.222)
        pre-merge-into-trunk            (revision: 1.173.2.70)
        BISON-1_29c                     (revision: 1.173.2.69)
        BISON-1_29b                     (revision: 1.173.2.56)
        BISON-1_29a                     (revision: 1.173.2.44)
        BISON-1_29                      (revision: 1.173.2.27)
        BISON-1_28d                     (revision: 1.173.2.24)
        bison-1_29-branch               (branch: 1.173.2)
        BISON-1_28c                     (revision: 1.173)
        BISON-1_28b                     (revision: 1.143)

As you can see, there is only 1 branch: bison-1_29-branch.
So in order to commit, you'll have to do

  cvs update -r bison-1_29-branch

(or a fresh checkout using that branch, that's up to you).