Vincent van Ravesteijn <v...@lyx.org> writes:
>> Now you can look around in this repo and see what the result is like.
>
| I like it.
>
>> I know of one small mistake, I misspelled Josès surname.
>
| I'm annoyed by the capitals only in the email address of Georg.Baum
| (but well that's nitpicking).
Easy enough to lowercase. I didn't notice.
>> Also a couple of tags are missing, they are a bit cumbersome (based on
>> mixed revisions and local wc changes).
>
| I see a tag "2.6.4.1" which should be "1.6.4.1".
Yeah I noticed as well. fixed.
| These might be the cumbersome tages, but "1.2.0", "1.4.5.1", "1.6.8",
| "1.5.3" seem to be missing.
Yes some of those are a bit problematic.
>> Please comment.
>> (also if my recipe does not work)
>>
>> (The bundle also contains the branches/tags that I do not plan to
>> provide in the final converted repo. These are not cloned by default.)
>> )
>
| A lot of tags that were destined to be removed are cloned anyway. It
| seems a bit random though which tags are cloned and which are not.
Not random at all. All are manually tagged so that they can be cloned.
| For
| example, there are 1.5.0alpha1 and 1.5.0rc2, but not 1.5.0rc1.
Only because I missed those, several tags look very weird in the repo,
basically due to cvs (and cvs2svn).
I missed several others as well. And end of this mail is the list of
tags that I have in my repo now.
I think I am down to only one really problematic tag now (or perhaps
two): 1.4.0 and 1.6.8
1.6.8 - because the 1.6.8 branch (read: svn tag) seems to be made from
a wc with local changes. This is the diff from where I really want to
place the tag:
diff --git a/ANNOUNCE b/ANNOUNCE
index f5276aa..d8c87f7 100644
--- a/ANNOUNCE
+++ b/ANNOUNCE
@@ -70,9 +70,6 @@ want to apply one of the following patches instead:
ftp://ftp.lyx.org/pub/lyx/stable/1.6.x/patch-1.6.8.gz
ftp://ftp.lyx.org/pub/lyx/stable/1.6.x/patch-1.6.8.bz2
-Note that for this release, some binaries have been added that are not produced
-by the patch.
-
If you find what you think is a bug in LyX 1.6.8, you may either
e-mail the LyX developers' mailing list (lyx-devel <at> lists.lyx.org),
or open a bug report at http://www.lyx.org/trac/
I am inclined to ignore this difference and place the tag in the best
spot, instead of where it would be "correct". The diff above will then
added in the next commit after the 1.6.8 tag.
1.4.0pre5 is also problematic. Created from a mixed revision wc it
seems. (I wonder how cvs made that happen...)
I am inclined to put the tag in the "best" spot. Will be a bit unice in
that if you build from the tag the the resulting binary will not call
itself 1.4.0pre5 but 1.4.0svn.
Similar with 1.4.0pre6.
And with 1.4.0 as well, this is especially bad. It might be possible to
fixup this with grafting, not sure if it is worth the effort though.
Current list of tags:
1.1.1
1.1.1pre2
1.1.2
1.1.3
1.1.4
1.1.5
1.1.5fix1
1.1.5fix2
1.1.5pre1
1.1.5pre2
1.1.5pre3
1.1.6
1.1.6fix1
1.1.6fix2
1.1.6fix3
1.1.6fix4
1.1.6pre1
1.1.6pre2
1.1.6pre3
1.2.0
1.2.0pre1
1.2.0pre2
1.2.0pre3
1.2.0pre4
1.2.0pre5
1.2.0rc1
1.2.1
1.2.2
1.2.3
1.3.0
1.3.0pre1
1.3.0pre2
1.3.0pre3
1.3.1
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.4.0pre1
1.4.0pre2
1.4.0pre3
1.4.0pre4
1.4.0pre5
1.4.1
1.4.2
1.4.3
1.4.4
1.4.5
1.4.5.1
1.5.0
1.5.0alpha1
1.5.0rc2
1.5.1
1.5.2
1.5.3
1.5.4
1.5.5
1.5.6
1.5.7
1.6.0
1.6.0alpha1
1.6.0alpha2
1.6.0beta1
1.6.0beta2
1.6.0beta3
1.6.0beta4
1.6.0rc1
1.6.0rc2
1.6.0rc3
1.6.0rc4
1.6.0rc5
1.6.1
1.6.10
1.6.2
1.6.3
1.6.4
1.6.4.1
1.6.5
1.6.6
1.6.7
1.6.8
1.6.9
2.0.0
2.0.0alpha1
2.0.0alpha2
2.0.0alpha3
2.0.0alpha4
2.0.0alpha5
2.0.0alpha6
2.0.0beta1
2.0.0beta2
2.0.0beta3
2.0.0beta4
2.0.0beta5
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
--
Lgb
