X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Thu, 8 Mar 2012 10:32:06 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: rebase keeps last modification time of DLL unchanged Message-ID: <20120308093206.GR5159@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4F57DC0F.2090401@t-online.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4F57DC0F.2090401@t-online.de> User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Mar 7 23:07, Christian Franke wrote: > The rebase tool does not change last modification timestamp of each > DLL even if its data has changed. This is likely because Windows > "may" not update the timestamp for files written through a memory > mapped view. > > Is this an intended behavior of rebase? Why should rebase change the timestamp? Apart from the rebasing, the DLL is still the same. If you want to know when it has been last rebased, you can look into the file header: $ objdump -p cygiconv-2.dll | grep 'Time/Date[^ ]' Time/Date Tue Mar 6 23:24:12 2012 Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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