Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: David Carlton <carlton@math.stanford.edu>, gdb@sources.redhat.com
Subject: Re: branching
Date: Thu, 19 Sep 2002 13:12:00 -0000	[thread overview]
Message-ID: <20020919201154.GA6607@nevyn.them.org> (raw)
In-Reply-To: <1020919200745.ZM22299@localhost.localdomain>

On Thu, Sep 19, 2002 at 01:07:46PM -0700, Kevin Buettner wrote:
> On Sep 19, 12:35pm, David Carlton wrote:
> 
> > > Maybe I'm being naive, but why can't you just checkout your branch,
> > > and then do:
> > 
> > >     cvs update -j HEAD
> > 
> > Ah: maybe that's part of the answer: maybe I should do
> > 
> >   cvs update -j carlton-dictionary-YYYYMMDD-tag -j HEAD
> > 
> > (I'd missed the keyword HEAD.)
> > 
> > Section 5.7 of the CVS manual suggests that what you say isn't a good
> > idea, because it claims that CVS will try to merge in all changes to
> > head since the original branch, rather than all changes since I last
> > merged.
> 
> I see.  That sounds right.
> 
> > If that's accurate, I need to get tags on the head somehow so
> > that it doesn't try to merge in changes twice.
> 
> Maybe just keep track of the date of the last merge and do:
> 
>     cvs update -j HEAD:date -j HEAD
> 
> Another approach might be to use the -F option with ``cvs tag'' so that
> you only need one merge tag (for your branch) on the mainline.
> 
> (If you try the -j HEAD:date approach, let me know how it works...)

It should work fine... but if you do that, specify an explicit date on
both.  It makes it much simpler to do the next merge.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-09-19 20:12 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                   ` Daniel Jacobowitz [this message]
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                   ` branching Keith Seitz
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=20020919201154.GA6607@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=carlton@math.stanford.edu \
    --cc=gdb@sources.redhat.com \
    --cc=kevinb@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