From: mike <mikereape@onetel.com>
To: cygwin@cygwin.com
Subject: Re: "rebase-trigger full"
Date: Tue, 25 Jul 2017 17:45:00 -0000 [thread overview]
Message-ID: <236f08d8-a329-cd9f-04ab-a0bb9d47a889@onetel.com> (raw)
In-Reply-To: <27503828-70f4-aad6-2e04-408676108403@gmail.com>
On 25/07/2017 15:29, Marco Atzeri wrote:
> On 25/07/2017 16:12, mike wrote:
>> On 25/07/2017 11:17, mike wrote:
>>> On 25/07/2017 06:21, Brian Inglis wrote:
>>>
>> Thanks very much for that Brian. That seems to have done the trick.
>> It's solved part of my problems anyway. However why does rebasing take
>> such a long time? I would have thought that it would be quite fast
>> using oldschool compile/link/load techniques. I'm not being critical I'm
>> just curious because a long time ago I used to work on stuff like this
>> myself.
>>
>
> Hi Mike,
>
> "full" take long as need to rebase from scratch every single dll's.
> It is only needed in case of problems.
>
> If you want to know how many dll's are rebased :
>
> $ rebase -si |wc -l
>
>
> The usual rebase pass is incremental and it is much faster.
>
> Regards
> Marco
>
>
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>
>
Thank you Marco. Maybe there are just way more dlls than I ever realised.
Mike
--
I *AM* a unique and special snowflake
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-07-25 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 5:11 mike
2017-07-25 14:29 ` Brian Inglis
2017-07-25 14:38 ` mike
2017-07-25 16:10 ` mike
2017-07-25 16:47 ` Marco Atzeri
2017-07-25 17:45 ` mike [this message]
2017-07-26 0:09 ` Achim Gratz
2017-07-26 8:09 ` mike
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=236f08d8-a329-cd9f-04ab-a0bb9d47a889@onetel.com \
--to=mikereape@onetel.com \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).