> This repo is clean and I believe it's ready to be used for
> production.
Excellent! Thanks a lot, Eric, the git conversion looks very good
now. If noone objects, please proceed and upload it to Savannah.
Werner
Werner LEMBERG :
>
> > This repo is clean and I believe it's ready to be used for
> > production.
>
> Excellent! Thanks a lot, Eric, the git conversion looks very good
> now. If noone objects, please proceed and upload it to Savannah.
Will do, but I'll give it a few days for Keith and others t
Using try 2, after git fast-import, du(1) shows:
260444 groff-git/.git/objects/pack
after git gc --aggressive, that becomes:
11632 groff-git/.git/objects/pack
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
James Cloos :
> Using try 2, after git fast-import, du(1) shows:
>
> 260444 groff-git/.git/objects/pack
>
> after git gc --aggressive, that becomes:
>
>11632 groff-git/.git/objects/pack
Right you are. Sorry, I forgot the pack stage. Doing that now.
--
http://www.catb.
> A point about development practice: I believe that in a
> version-control system with real changesets, the ChangeLog
> convention is obsolete. The whole-commit information that went in
> ChangeLog entries now naturally lives in per-changeset comments.
>
> Can you think of any reason I shouldn'
Werner LEMBERG :
> Right now, I would like to stay with ChangeLog entries in the usual
> way. A new maintainer might change this, say, to use git commit
> entries only, generating a ChangeLog file automatically. IMHO, the
> right time to do such a switch is immediately after a new release.
Noted
> Do you have any plans to ship a wrap-up 1.23 before you step out of
> the frame?
If time permits, I would like to apply a couple of patches after the
migration to git. I guess it would make sense to release 1.23 in the
end of this year.
Werner
