how to access the whole csv repository - XEmacs-Beta - XEmacs Mailing List Archives

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

how to access the whole csv repository

Summary of XEmacs Issue Tracking...

Summary of XEmacs Issue Tracking...

Uwe Brauer

Friday, 17 August 2018 Fri, 17 Aug '18

1:45 p.m.

(permalink)

Hi I'd like to try, out of curiosity to access the old csv xemacs repo, to see how it can be converted in a better way to mercurial. Anybody knows pointer. I am looking in the webarchive but cannot find it. Uwe Brauer

Attachments:

smime.p7s (application/pkcs7-signature — 4.9 KB)

Reply

Show replies by thread

Mats Lidell

Saturday, 18 August Sat, 18 Aug

11:48 a.m.

(permalink)

Hi Uwe,

Uwe Brauer writes: I'd like to try, out of curiosity to access the old csv xemacs repo, to see how it can be converted in a better way to mercurial.

I don't know about the CVS archive I'm afraid but I'm curious what you mean with converting it in a better way to mercurial. What is missing in the current one? Yours Mats

Reply

Uwe Brauer

Saturday, 18 August Sat, 18 Aug

1:38 p.m.

(permalink)

>> "Mats" == Mats Lidell <mats.lidell(a)cag.se> writes:

Hi Mats

Hi Uwe, > Uwe Brauer writes: > I'd like to try, out of curiosity to access the old csv xemacs repo, to > see how it can be converted in a better way to mercurial.

I don't know about the CVS archive I'm afraid but I'm curious what you mean with converting it in a better way to mercurial. What is missing in the current one?

Well for me one of the most useful commands is hg log -G Which gives me a graphic idea about the history of the repository. (I am also a fan of named branches, but this is a different topic). What I find confusing though is to see several «branches» in a repo which do not correspond really to branches. To illustrate my point Please try hg log -G | grep 9624523604c5 Or hg log | grep 9624523604c5 And you will see something very odd. I presume this was generated by the conversion from CVS to mercurial and that is why I wanted to know with which tools the conversation was done, and where to find the original CVS. I hoped to have a backup but I don't. Uwe

Reply

Aidan Kehoe

Sunday, 26 August Sun, 26 Aug

9:26 p.m.

(permalink)

Ar an t-ochtú lá déag de mí Lúnasa, scríobh Uwe Brauer:

Which gives me a graphic idea about the history of the repository. (I am also a fan of named branches, but this is a different topic). What I find confusing though is to see several «branches» in a repo which do not correspond really to branches. To illustrate my point Please try hg log -G | grep 9624523604c5 Or hg log | grep 9624523604c5 And you will see something very odd. I presume this was generated by the conversion from CVS to mercurial and that is why I wanted to know with which tools the conversation was done, and where to find the original CVS.

No, those changes were made directly in Mercurial, and it was intentional, Ben was doing a lot of work parallel to the trunk, with intermittent merging of changes back and forth. This was distributed development working well. The trunk has been in Mercurial since December 2007. The other repositories moved to CVS more slowly. There are problems with the CVS import, among them that changeset number 426, id 43177a4f3daf removed all the C files(!), so most of the C files look like they date from changeset 428 on hg annotate. I have a suspicion that dated from the underlying CVS tree, though. I don’t know of a copy of the underlying CVS repository. They were last hosted on alioth.debian.org, which is no longer available. -- ‘As I sat looking up at the Guinness ad, I could never figure out / How your man stayed up on the surfboard after forty pints of stout’ (C. Moore)

Reply

Uwe Brauer

Monday, 27 August Mon, 27 Aug

7:39 a.m.

(permalink)

Ar an t-ochtú lá déag de mí Lúnasa, scríobh Uwe Brauer:

No, those changes were made directly in Mercurial, and it was intentional, Ben was doing a lot of work parallel to the trunk, with intermittent merging of changes back and forth. This was distributed development working well.

Oops, so five different branches. What seems odd to me that these branches were not named branches, but anonymous and that there were/are not even bookmarks. To work with 5 different anonymous heads looks very messy to me. An option would be to use the remotebookmark extension and to add bookmarks to those branches. In my opinion bookmarks are a kludge, but this is a controversial topic. I am not sure that with the evolve extension one could change these anonymous branches to named ones. I could ask on the mercurial list if there is interest in the issue.

The trunk has been in Mercurial since December 2007. The other repositories moved to CVS more slowly.

There are problems with the CVS import, among them that changeset number 426, id 43177a4f3daf removed all the C files(!), so most of the C files look like they date from changeset 428 on hg annotate. I have a suspicion that dated from the underlying CVS tree, though.

I don’t know of a copy of the underlying CVS repository. They were last hosted on alioth.debian.org, which is no longer available.

Ok. Uwe

Reply

2062

days inactive

2072

days old

xemacs-beta@xemacs.org

Manage subscription

4 comments

3 participants

tags (0)

participants (3)

Aidan Kehoe
Mats Lidell
Uwe Brauer