>> [...] I just got a message that the CVS files from 1999 on ffii are
>> lost due to physical damage of the backups in 2001.
>
> I guess we go with what we have, then.
Yes! Eric, you have now administrator rights for the groff project;
I've also activated git. Please proceed, and thanks for yo
Werner LEMBERG :
> >> I've released them within a very short time, due to bugs.
> >>
> >> 1.121999-12-14
> >> 1.12.1 1999-12-22
> >> 1.131999-12-23
> >> 1.141999-12-26
> >
> > Can you reconstruct any of the missing ones from base + xdelta?
>
> No, sorry. And I just got a me
>> I've released them within a very short time, due to bugs.
>>
>> 1.121999-12-14
>> 1.12.1 1999-12-22
>> 1.131999-12-23
>> 1.141999-12-26
>
> Can you reconstruct any of the missing ones from base + xdelta?
No, sorry. And I just got a message that the CVS files from 1999 on
Werner LEMBERG :
>
> > 01 is missing from that list, is that because it's a buggy release?
>
> We don't know.
>
> > 12 and 13 appear missing, or did they never get released?
>
> I've released them within a very short time, due to bugs.
>
> 1.121999-12-14
> 1.12.1 1999-12-22
> 1.13
> 01 is missing from that list, is that because it's a buggy release?
We don't know.
> 12 and 13 appear missing, or did they never get released?
I've released them within a very short time, due to bugs.
1.121999-12-14
1.12.1 1999-12-22
1.131999-12-23
1.141999-12-26
There
Hi Eric,
> groff-1.02.tar.Z
> groff-1.02.tar.Z.sig
> groff-1.04.tar.Z
> groff-1.04.tar.Z.sig
> groff-1.05.tar.Z
> groff-1.05.tar.Z.sig
> groff-1.06.tar.gz
> groff-1.06.tar.gz.sig
> groff-1.08.tar.gz
> groff-1.08.tar.gz.sig
> groff-1.09.tar.gz
> groff-1.09.tar.gz.sig
> groff-1.10.tar.gz
> groff-1.1
Ralph Corderoy :
> http://www.informatica.co.cr/unix/research/1991/0115.htm refers to 1.00
> and 1.01 but I haven't come across them anywhere.
>
> Tell us what you've got and perhaps list members can have a poke around
> for what else they have.
groff-1.02.tar.Z
groff-1.02.tar.Z.sig
groff-1.04.ta
> Are you aware of the 1.02 onwards in
>
> ftp://prep.ai.mit.edu/pub/gnu/groff/old/
> ftp://prep.ai.mit.edu/pub/gnu/groff/
Yeah, I've uploaded what had found in the net.
Werner
Hi Eric,
> In that case, the metadata hacking is all done. All that's left to
> determine is how much prehistoric daya we can find and glue to the
> front of the repo.
Are you aware of the 1.02 onwards in
ftp://prep.ai.mit.edu/pub/gnu/groff/old/
ftp://prep.ai.mit.edu/pub/gnu/groff/
htt
Werner LEMBERG :
> Please leave it as-is.
Will do.
In that case, the metadata hacking is all done. All that's left to determine
is how much prehistoric daya we can find and glue to the front of the repo.
--
http://www.catb.org/~esr/";>Eric S. Raymond
> transform 1..$ /^\n\* (.*)\n\n$/\n\1\n\n/
>
> The reason for this is that I think it would be good if leading '*'
> in a gitk list of first lines were a visual warning that the
> following comment is "old style" - fails to obey git conventions
>
> The policy question is: are you OK with me edi
Werner LEMBERG :
> > For your interest, and so you and the other listmembers can see how
> > this was done, I'm enclosing a tarball containing copies of the
> > current authormap file (which is what you modified, with five
> > entries added and some address removals reverted), the reposurgeon
> > l
> For your interest, and so you and the other listmembers can see how
> this was done, I'm enclosing a tarball containing copies of the
> current authormap file (which is what you modified, with five
> entries added and some address removals reverted), the reposurgeon
> lift script, and the Makefi
Werner LEMBERG :
> However, the last entry before that was
>
> Fri Aug 15 08:51:47 1997 Eric S. Raymond
>
> * README, PROJECTS, NEWS, INSTALL, VERSION,
> doc/Makefile. doc/pic.ms, groff/groff.man:
> Prepare for 1.11 release. No code changes.
> Documentation
> You were either very lucky or very careful; most CVS repos of any
> age have a lot more cruft in them than this.
:-) It's probably due to my aversion to branches, at least with CVS...
> What happened to the history before 2000?
Honestly, I don't know; see my other e-mail. Looking up the grof
Compared to most CVS conversions this one was almost ridiculously easy;
cvs-fast-export and reposurgeon made short work of it. (I improved
both slightly in the process, which is normal; every repo, even the
easy ones, is a different challenge.)
The git conversion is nearly linear, with one root,
16 matches
Mail list logo
