Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Keith Seitz <keiths@redhat.com>,
	Kevin Buettner <kevinb@redhat.com>,
	gdb@sources.redhat.com
Subject: Re: branching
Date: Fri, 20 Sep 2002 17:18:00 -0000	[thread overview]
Message-ID: <3D8BBAD3.3020900@ges.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0209200125170.6279-100000@dberlin.org>

> 
> In fact, if you really want to be advanced, and not deal with the 
> slowdown on merged files that haven't been modified by you on the branch, 
> but have been on the merge (This is hard to explain. If you merge from 
> the head, and commit the result, it makes a new revision in the file, 
> even if you haven't made changes on the branch. This eventually makes 
> accessing the branch *quite* slow), you can just move the branch tags on 
> the files you haven't modified on the branch, so that they refer to the 
> new mainline revision.
> 
> Sounds more difficult complex than it is.

You don't happen to have a script?  (Yes, for long lived branches things 
do start to get slow).  The other option is to fix CVS I guess.

Andrew



  reply	other threads:[~2002-09-21  0:18 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                       ` Andrew Cagney [this message]
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=3D8BBAD3.3020900@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=dberlin@dberlin.org \
    --cc=gdb@sources.redhat.com \
    --cc=keiths@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