Tags missing from GIT mirror?
in [PgSql]
|
From: Andrew Dunstan on 12 May 2010 16:11 Florian Pflug wrote: > On May 12, 2010, at 21:52 , Andrew Dunstan wrote: > >> David Christensen wrote: >> >>> Is there anything to do about the missing tags in git? I've wished for those to be available as well. >>> >>> >> Sure, fix fromcvs to emit them. How is your ruby? >> > > > Where does one find the version of fromcvs used to feed git.postgresql.org? I might give it a shot. > > I can't promise anything, though - my ruby-fu is OK, but my cvs-fu is badly lacking... > > > Fix the tip version. You'll need fromcvs and rcsparse from <http://ww2.fs.ei.tum.de/~corecode/hg>. We already know that the version used on the community repo is broken. The version I am using on my github mirror is holding up OK. There is a recipe for setting up a mirror on my blog: <http://people.planetpostgresql.org/andrew/index.php?/archives/74-Gory-details.html>. Of course, we might also find some other brokenness if we try to import all the tags. Also, be aware of this (from <http://cvs2svn.tigris.org/cvs2git.html>): Differences between CVS and git branch/tag models: CVS allows a branch or tag to be created from arbitrary combinations of source revisions from multiple source branches. It even allows file revisions that were never contemporaneous to be added to a single branch/tag. Git, on the other hand, only allows the full source tree, as it existed at some instant in the history, to be branched or tagged as a unit. Moreover, the ancestry of a git revision makes implications about the contents of that revision. This difference means that it is fundamentally impossible to represent an arbitrary CVS history in a git repository 100% faithfully. cheers andrew -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Florian Pflug on 12 May 2010 16:18 On May 12, 2010, at 22:03 , Tom Lane wrote: > Andrew Dunstan <andrew(a)dunslane.net> writes: >> David Christensen wrote: >>> Is there anything to do about the missing tags in git? I've wished for those to be available as well. > >> Sure, fix fromcvs to emit them. How is your ruby? > > Per Magnus' comment, there isn't anything "missing". We don't make > branches for beta releases. (Personally I'm thinking that having stub > branches for the alphas was a mistake too --- obviously, it's leading to > confusion.) Yeah, but CVS has tags for the alphas and betas. Those are missing from the GIT mirror as the CVS-to-GIT converter apparently ignores tags completely :-(. Since there are no branches for the betas, this leaves the GIT repository without any trace that beta1 exists at all... So there is nothing wrong with the CVS, but on the GIT side there is certainly room for improvement. best regards, Florian Pflug -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Tom Lane on 12 May 2010 16:22 Florian Pflug <fgp(a)phlo.org> writes: > Yeah, but CVS has tags for the alphas and betas. Those are missing from the GIT mirror as the CVS-to-GIT converter apparently ignores tags completely :-(. Since there are no branches for the betas, this leaves the GIT repository without any trace that beta1 exists at all... Really? Then it wouldn't know about any past point-releases either :-( regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Andrew Dunstan on 12 May 2010 16:30 Tom Lane wrote: > Andrew Dunstan <andrew(a)dunslane.net> writes: > >> David Christensen wrote: >> >>> Is there anything to do about the missing tags in git? I've wished for those to be available as well. >>> > > >> Sure, fix fromcvs to emit them. How is your ruby? >> > > Per Magnus' comment, there isn't anything "missing". We don't make > branches for beta releases. (Personally I'm thinking that having stub > branches for the alphas was a mistake too --- obviously, it's leading to > confusion.) > > > What's missing is a non branch tag. It's there in CVS and not in the git repos. cheers andrew -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Andrew Dunstan on 12 May 2010 16:36 Tom Lane wrote: > Florian Pflug <fgp(a)phlo.org> writes: > >> Yeah, but CVS has tags for the alphas and betas. Those are missing from the GIT mirror as the CVS-to-GIT converter apparently ignores tags completely :-(. Since there are no branches for the betas, this leaves the GIT repository without any trace that beta1 exists at all... >> > > Really? Then it wouldn't know about any past point-releases either :-( > > > Presumably when we cut over to git properly, we will use some other tool that does import non-branch tags. But for now fromcvs is effectively the only game in town for incremental mirroring. Of course, if someone fixed it to handle tags that would be cool ... cheers andrew -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 Prev: [HACKERS] Tags missing from GIT mirror? Next: multibyte charater set in levenshtein function |