[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    Re: kdenetwork/kmail
From:       Zack Rusin <zack () kde ! org>
Date:       2003-01-15 1:13:10
[Download RAW message or body]

On Tuesday 14 January 2003 19:16, Marc Mutz wrote:
> On Wednesday 15 January 2003 01:20, Cornelius Schumacher wrote:
> <snip>
>
> > Well, probably the only really valid reason is that the history
> > contains the fact that the file was renamed.
>
> <snip>
>
> One doesn't rename files for fun. It's done in two scenarios:
>
> 1. Changing the directory structure (incl. cross-module moves)
> 2. Renaming the corresponding class.
>
> This here is about case 2. So any renaming of files in scenario 2
> comes with accompanying commits to
>
> a. files that #include the renamed file's header
> b. the renamed file itself, to rename the class or whatever prompted
> the rename of the file in the first place.

OK guys, I made the mistake (not the first today) I figured that 
bothering admins to move history for a file with a very limited history 
in the first place doesn't make sense and renaming it the raw way won't 
bother anyone. Obviously it does so David could you move the history? I 
haven't made any changes to recentaddresses.[h|cpp] since the rename so 
if you could add the history from kmrecentaddr.[h|cpp] I'd really 
appreciate it. 
Sorry for the inconvenience everyone.

Zack

-- 
Any sufficiently advanced technology is indistinguishable from a perl
script.

[prev in list] [next in list] [prev in thread] [next in thread]