This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Making your branches smaller for easier merges


> 
> 
> Sorry, I still don't see where is the problem. You either want the
> extension in your branch, so you merge it and simply update libstdc++,
> or you don't want the extension just yet, so you just don't update
> libstdc++ (or update back to your previous revision).
That means you have to follow what is going on the mainline closer than
you would if you just branched the whole sources.  Yes changes like this
has happened for 4.2.0 even.  Since you branched the GCC directory for
non front-end changes like say a new opimization, you don't want to follow
what is happening on the C++ front-end side that closely .Also you don't know
if it was too late to update until you actually did it.

-- Pinski



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]