Re: [avr-libc-dev] boot.h and -mint8

[Theodore A. Roth]

On Thu, 18 Sep 2003 address@hidden wrote:

> >
> >
> > On Thu, 18 Sep 2003, E.Weddington wrote:
> >
> > > > Start with this:
> > > >
> > > >   http://mail.nongnu.org/archive/html/avr-libc-
> dev/2003-
> > > 08/msg00012.html
> > > >
> > > > Hint: I keep HEAD in avr-libc-cvs.
> > > >
> > > > Ted Roth
> > > >
> > >
> > > Ok, I new about the tag name, but let's see if I
> understand
> > > what the process is:
> > >
> > > [All -d flags are ignored for brevity.]
> > > 1. Check out 1.0 branch
> > > cvs co -r avr-libc-1_0-branch avr-libc
> > > 2. Apply patch, check in changes.
> > > cvs commit -m "message" boot.h
> > > 3. Check out HEAD (in a clean dir)
> > > cvs co -r avr-libc-cvs avr-libc
> > > [is this right?]
> > > 4. Apply patch, check in changes.
> > > cvs commit -m "message" boot.h
> > >
> > > I really don't want to screw this up.
> >
> > Close, but not quite right.
> >
> > You should already have HEAD. That's what you get from a
> checkout
> > without the "-r tag" spec.
> >
> > By default, all checkouts of the "avr-libc" module will
> create a
> > "avr-libc" directory. My hint was to take that and rename
> it to
> > avr-libc-cvs to avoid clobbering it with a subsequent
> checkout.
> >
> > Basically, I have one tree for HEAD (named avr-libc-cvs)
> and one tree
> > for the branch (named avr-libc-1.0-cvs).
> >
> > So, assuming you already have HEAD checked out, just
> rename it to
> > avr-libc-cvs. If you need to get a fresh copy, the just
> use:
> >
> >   $ cvs -d <foo> co avr-libc
> >   $ mv avr-libc avr-libc-cvs
> >
> > Now you can safely checkout avr-libc again (and again,
> etc) without
> > hosing work in progress. In theory, you can have 100's of
> trees
> > checked out. Sometimes I have just do new checkout to
> play with
> > patches in an isolated way.
> >
> > Grabbing the branch is now as you state in 1) about. To
> verify that
> > you really did checkout the branch, run cvs status -v on
> a file in the
> > tree and you should see a sticky tag with the branch tag.
> >
> > I'd recommend committing patches to HEAD before the
> branch so you see
> > if anything went wrong.
> >
>
> Ok, committed to HEAD and branch. Viewing via WebCVS look
> like everything is ok, but let me know if there any
> problems. Thank you very much for your help in this!

Looks fine.

Ted Roth