Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: gdb@sources.redhat.com
Subject: Re: branching
Date: Thu, 19 Sep 2002 14:52:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0209191452480.1407-100000@valrhona.uglyboxes.com> (raw)
In-Reply-To: <ro17khhwvxb.fsf@jackfruit.Stanford.EDU>

On 19 Sep 2002, David Carlton wrote:

> Great, glad to hear I'm on track.  Could you tell me exactly what you
> type to create the merge tags on the mainline and to update your
> branch to reflect the changes between two mainline merge tags?  (And
> whatever words of wisdom you have on the subject of, when you use cvs
> rtag to create a tag, what branch(es?) that tags applies to, would be
> greatly appreciated.)

Sure. To create the symbol tag in mainline (I use rtag, since it will tag 
the repository copy, not any local copy):
$ cvs rtag kseitz_interps-DATE-merge gdb+dejagnu

Then to apply the tag to my branch, I "cd" into my branch sources
$ cd my-branch/src
$ cvs -q update -j kseitz_interps-LASTDATE-merge  \
  -j kseitz_interps-DATE-merge gdb+dejagnu

Finally resolve any conflicts and "cvs ci". 
 
> And, given that I'm probably temperamentally suited to relatively
> frequent merges, I'll want to take Kevin's advice and delete merge
> tags that I haven't used for a while.

Hmm, yeah, I guess I should do that, too.

Keith



  reply	other threads:[~2002-09-19 21:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ro1fzw9h8r2.fsf@jackfruit.Stanford.EDU>
     [not found] ` <20020917143553.GA28408@nevyn.them.org>
     [not found]   ` <ro1k7lkfr5d.fsf@jackfruit.Stanford.EDU>
     [not found]     ` <20020917174928.GA23058@nevyn.them.org>
     [not found]       ` <ro165x4fotl.fsf@jackfruit.Stanford.EDU>
     [not found]         ` <3D87815A.4010807@ges.redhat.com>
2002-09-19 12:12           ` branching David Carlton
2002-09-19 12:30             ` branching Kevin Buettner
2002-09-19 12:35               ` branching David Carlton
2002-09-19 13:07                 ` branching Kevin Buettner
2002-09-19 13:12                   ` branching Daniel Jacobowitz
2002-09-19 13:07               ` branching Keith Seitz
2002-09-19 13:11                 ` branching Kevin Buettner
2002-09-19 13:19                   ` branching Keith Seitz
2002-09-19 22:29                     ` branching Daniel Berlin
2002-09-20 17:18                       ` branching Andrew Cagney
2002-09-20 17:45                         ` branching Daniel Berlin
2002-09-19 13:45                 ` branching David Carlton
2002-09-19 14:52                   ` Keith Seitz [this message]
2002-09-19 15:10                     ` branching David Carlton
2005-02-12  4:24 Branching Russell Shaw
2005-02-13  0:10 Branching Paul Schlie
2005-02-13 11:14 ` Branching Russell Shaw

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.44.0209191452480.1407-100000@valrhona.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=carlton@math.stanford.edu \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox