Re: move to git

Jim Meyering <[EMAIL PROTECTED]> writes: > I gave up on git-cvsimport a while ago, since it was so slow > compared to parsecvs, but mainly because it would actually *reverse* > revisions some time. E.g., it would sometimes put CVS version 1.2 > before 1.1. That's a cvsps problem, not specific to

Re: move to git

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > * Jim Meyering wrote on Sat, Apr 19, 2008 at 11:53:23AM CEST: >> I'm beginning to think that our time might be better spent >> investigating an alternate conversion method: cvs2git. >> Unfortunately, I might not have time for that right away. > > Are the

Re: move to git

Hi Jim, * Jim Meyering wrote on Sat, Apr 19, 2008 at 11:53:23AM CEST: > I'm beginning to think that our time might be better spent > investigating an alternate conversion method: cvs2git. > Unfortunately, I might not have time for that right away. Are there known deficiencies of git cvsimport? (I

Re: move to git

"Dan Nicholson" <[EMAIL PROTECTED]> wrote: > On Sat, Apr 19, 2008 at 2:53 AM, Jim Meyering <[EMAIL PROTECTED]> wrote: >> >> Ralf Wildenhues <[EMAIL PROTECTED]> wrote: >> >> > I don't quite understand what happened. With the repo converted from >> > CVS, the tag SHAs were all different, but they

Re: move to git

On Sat, Apr 19, 2008 at 2:53 AM, Jim Meyering <[EMAIL PROTECTED]> wrote: > > Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > > I don't quite understand what happened. With the repo converted from > > CVS, the tag SHAs were all different, but they already pointed to the > > same tree object. Aft

Re: move to git

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > * Andreas Schwab wrote on Sat, Apr 19, 2008 at 12:14:12AM CEST: >> Ralf Wildenhues <[EMAIL PROTECTED]> writes: >> >> > GNU Libtool's primary source repository is now managed with git: >> > >> > >> > Note that

Re: move to git

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > I don't quite understand what happened. With the repo converted from > CVS, the tag SHAs were all different, but they already pointed to the > same tree object. Did they? Then the CVS import was already broken, since the tags definitely denote diffe

Re: move to git

* Andreas Schwab wrote on Sat, Apr 19, 2008 at 12:14:12AM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > > GNU Libtool's primary source repository is now managed with git: > > > > > > Note that there were several conversions, so the current rep

Re: move to git

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > GNU Libtool's primary source repository is now managed with git: > > > Note that there were several conversions, so the current repo has been > rewound and is not a continuation of the earlier, read-only git

Re: move to git

"Gary V. Vaughan" <[EMAIL PROTECTED]> writes: > So my question is how did you find the stale tags? Try browsing with gitk --all. You will soon notice the tags that are heads by itself, instead of marking a commit on the ancestry of an existing head. Also, "git merge-base master release-2-2-2" d

Re: move to git

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Gary V. Vaughan on 4/16/2008 7:31 PM: | Ah, the link that was giving me a 403 was picking up a spurious trailing | paren. So now I see two near identical pages: | | http://git.sv.gnu.org/gitweb/?p=libtool.git;a=commit;h=2bbe5d | http://g

Re: move to git

On 16 Apr 2008, at 18:04, Ralf Wildenhues wrote: Hello Eric, Gary, Hallo Ralf, * Gary V. Vaughan wrote on Wed, Apr 16, 2008 at 11:51:48PM CEST: On 16 Apr 2008, at 16:47, Eric Blake wrote: there are now some stale tags in savannah's libtool.git, which point to commits prior to your various g

Re: move to git

On Wed, Apr 16, 2008 at 3:07 PM, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > Hi Dan, > > * Dan Nicholson wrote on Thu, Apr 17, 2008 at 12:01:00AM CEST: > > > On Wed, Apr 16, 2008 at 2:51 PM, Gary V. Vaughan <[EMAIL PROTECTED]> wrote: > > > > a-machine-with-git$ git-clone http://git.sv.gnu.org/l

Re: move to git

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > Hello Eric, Gary, > > * Gary V. Vaughan wrote on Wed, Apr 16, 2008 at 11:51:48PM CEST: >> On 16 Apr 2008, at 16:47, Eric Blake wrote: >>> there are now some stale tags >>> in savannah's libtool.git, which point to commits prior to your >>> various gi

Re: move to git

Hi Dan, * Dan Nicholson wrote on Thu, Apr 17, 2008 at 12:01:00AM CEST: > On Wed, Apr 16, 2008 at 2:51 PM, Gary V. Vaughan <[EMAIL PROTECTED]> wrote: > > a-machine-with-git$ git-clone http://git.sv.gnu.org/libtool.git libtool > > a-machine-with-git$ scp libtool [EMAIL PROTECTED]: > > a-machin

Re: move to git

Hello Eric, Gary, * Gary V. Vaughan wrote on Wed, Apr 16, 2008 at 11:51:48PM CEST: > On 16 Apr 2008, at 16:47, Eric Blake wrote: >> there are now some stale tags >> in savannah's libtool.git, which point to commits prior to your >> various git- >> filter operations (for example, the tag release-

Re: move to git

On Wed, Apr 16, 2008 at 2:51 PM, Gary V. Vaughan <[EMAIL PROTECTED]> wrote: > > Playing devil's advocate: > > If Libtool moves to git-version-gen ala Autoconf, it won't be possible to > do this > anymore: > > a-machine-with-git$ git-clone http://git.sv.gnu.org/libtool.git libtool > a-machine

Re: move to git

Hi Eric, On 16 Apr 2008, at 16:47, Eric Blake wrote: there are now some stale tags in savannah's libtool.git, which point to commits prior to your various git- filter operations (for example, the tag release-2-2-2 http://git.sv.gnu.org/gitweb/?p=libtool.git;a=tag;h=c7bb42 points to http://git

Re: move to git

Ralf Wildenhues gmx.de> writes: > Please do not continue to use the CVS repo. Its contents will soon be > replaced with a single file pointing to the git one. Ralf, thanks for the conversion work. However, there are now some stale tags in savannah's libtool.git, which point to commits prior t

move to git

Hello libtool list readers, GNU Libtool's primary source repository is now managed with git: Note that there were several conversions, so the current repo has been rewound and is not a continuation of the earlier, read-only git repo. Please do not con