kdelibs, kdebase moving to Git this Saturday

[Torgny Nyblom]

On Friday 28 January 2011 11.05.43 Johannes Sixt wrote:
> Am 1/28/2011 10:31, schrieb Torgny Nyblom:
> > On Friday 28 January 2011 00.06.21 Nicolas Alvarez wrote:
> >> John Tapsell wrote:
> >>> 2011/1/27 Nicolás Alvarez <nicolas.alvarez at gmail.com>:
> >>>> Please, help review the repositories before migration! Unlike KDE
> >>>> software, here we won't have point releases to fix bugs later :)
> >>> 
> >>> I have quite a few commits in kdebase-workspace with the commit
> >>> message:
> >>> 
> >>> SVN_SILENT:
> >>> Do blahblah
> >>> 
> >>> and
> >>> 
> >>> GUI:
> >>> do blah blah
> >>> 
> >>> 
> >>> Since git places a high important on the very first line, could we
> >>> mangle these into  "SVN_SILENT: Do blahblah"  and "GUI: do blah
> >>> blah"
> >> 
> >> It's technically possible, but it may involve a lot of manual work.
> >> 
> >> And many people (not including me) disagree with this kind of history
> >> edits; for example: "<Sho_> IMHO the objective is to import the SVN
> >> history faithfully and accurately"
> > 
> > While I agree with Eike here, I think that in this case we can make an
> > exception, however I do not like the idea of git-filter-branch. How
> > about we simply rewrite the message in svn2git?
> 
> Doesn't it operate with a git-fast-import stream? Wouldn't it just mean to
> flip a LF to a SP here and there? You wouldn't even have to change the
> byte-length of the commit messages.

Well yes, but that would potentionaly give us messages like "SVN_SILENT CCBUG: 
123456 BUG: 123455 Fix foo bar". Wouldn't it be better to move these messages 
to the end of the message if there is a valid line to show.

/Regards
Torgny