This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


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: ct-ng -> git repos instead of single patches


Hi,

On Tue, Aug 17, 2010 at 1:37 PM, Enrico Weigelt <weigelt@metux.de> wrote:
> But: then you've got now guarantee that the remaining will apply again.
> You'll have to get a fresh upstream tree and apply them all manually
> (unless you don't want to run the whole ct-ng machinery for half an
> hour just to find out that some patches failed). And if some patches
> failed, you'll have to manually replay the changes and diff them
> out again.
>
> In the end, this goes down to an rebase operation again - regardless
> if you're doing it manually or with the help of an proper vcs.
>
the effort should be spent getting the patch upstream, not finding a
way to easily move 250 patches from rev A to rev B. Yes, that's a much
more difficult effort.

 - Arnaud

--
For unsubscribe information see http://sourceware.org/lists.html#faq


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