Re: rebase keeps last modification time of DLL unchanged

2012-03-10 Thread Robert Miles
On 3/9/2012 1:47 PM, Corinna Vinschen wrote: On Mar 9 19:22, Christian Franke wrote: Christopher Faylor wrote: On Fri, Mar 09, 2012 at 09:43:07AM +0100, Corinna Vinschen wrote: On Mar 8 21:37, Christian Franke wrote: I'm not so sure this option would make a lot of sense. An option not used

Re: rebase keeps last modification time of DLL unchanged

2012-03-09 Thread Christopher Faylor
On Fri, Mar 09, 2012 at 09:09:41PM +0100, Corinna Vinschen wrote: >On Mar 9 14:55, Christopher Faylor wrote: >> On Fri, Mar 09, 2012 at 08:47:33PM +0100, Corinna Vinschen wrote: >> >On Mar 9 19:22, Christian Franke wrote: >> >> Christopher Faylor wrote: >> >> >I don't think the default should cha

Re: rebase keeps last modification time of DLL unchanged

2012-03-09 Thread Corinna Vinschen
On Mar 9 14:55, Christopher Faylor wrote: > On Fri, Mar 09, 2012 at 08:47:33PM +0100, Corinna Vinschen wrote: > >On Mar 9 19:22, Christian Franke wrote: > >> Christopher Faylor wrote: > >> >I don't think the default should change but maybe an option could be > >> >added for people who want to see

Re: rebase keeps last modification time of DLL unchanged

2012-03-09 Thread Christian Franke
Corinna Vinschen wrote: On Mar 9 19:22, Christian Franke wrote: Christopher Faylor wrote: On Fri, Mar 09, 2012 at 09:43:07AM +0100, Corinna Vinschen wrote: On Mar 8 21:37, Christian Franke wrote: rebase does not explicitly (re)set the timestamp after rebasing. Is this by design? Well, let

Re: rebase keeps last modification time of DLL unchanged

2012-03-09 Thread Christopher Faylor
On Fri, Mar 09, 2012 at 08:47:33PM +0100, Corinna Vinschen wrote: >On Mar 9 19:22, Christian Franke wrote: >> Christopher Faylor wrote: >> >On Fri, Mar 09, 2012 at 09:43:07AM +0100, Corinna Vinschen wrote: >> >>On Mar 8 21:37, Christian Franke wrote: >> >>>rebase does not explicitly (re)set the t

Re: rebase keeps last modification time of DLL unchanged

2012-03-09 Thread Corinna Vinschen
On Mar 9 19:22, Christian Franke wrote: > Christopher Faylor wrote: > >On Fri, Mar 09, 2012 at 09:43:07AM +0100, Corinna Vinschen wrote: > >>On Mar 8 21:37, Christian Franke wrote: > >>>rebase does not explicitly (re)set the timestamp after rebasing. Is > >>>this by design? > >>> > >>Well, let me

Re: rebase keeps last modification time of DLL unchanged

2012-03-09 Thread Christian Franke
Christopher Faylor wrote: On Fri, Mar 09, 2012 at 09:43:07AM +0100, Corinna Vinschen wrote: On Mar 8 21:37, Christian Franke wrote: Corinna Vinschen wrote: 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 ch

Re: rebase keeps last modification time of DLL unchanged

2012-03-09 Thread Christopher Faylor
On Fri, Mar 09, 2012 at 09:43:07AM +0100, Corinna Vinschen wrote: >On Mar 8 21:37, Christian Franke wrote: >> Corinna Vinschen wrote: >> >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

Re: rebase keeps last modification time of DLL unchanged

2012-03-09 Thread Corinna Vinschen
On Mar 8 21:37, Christian Franke wrote: > Corinna Vinschen wrote: > >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 wr

Re: rebase keeps last modification time of DLL unchanged

2012-03-08 Thread Christian Franke
Corinna Vinschen wrote: 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 intende

Re: rebase keeps last modification time of DLL unchanged

2012-03-08 Thread Corinna Vinschen
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 r

Re: rebase keeps last modification time of DLL unchanged

2012-03-07 Thread Adam Puckett
What happens when you `touch` the DLL? -- 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

rebase keeps last modification time of DLL unchanged

2012-03-07 Thread Christian Franke
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? Christian -- Problem reports: http