From: Shigeharu T. <sh...@ie...> - 2025-04-03 01:15:28
|
shige 04/03 2025 ---------------- Old gnuplot-1.1 is in SouceForge site. I found historical old gnuplot 1.0 (1.0.3). announce: https://usenet.trashworldnews.com/?thread=114748 1/6: https://usenet.trashworldnews.com/?thread=114473 2/6: https://usenet.trashworldnews.com/?thread=114532 3/6: https://usenet.trashworldnews.com/?thread=114531 4/6: https://usenet.trashworldnews.com/?thread=114530 5/6: https://usenet.trashworldnews.com/?thread=114529 6/6: https://usenet.trashworldnews.com/?thread=114528 I make the archive file of them (.tar.Z) http://takeno.iee.niit.ac.jp/~shige/unix/gnuplot/data/gnuplot-1.0.tar.Z +========================================================+ Shigeharu TAKENO NIigata Institute of Technology kashiwazaki,Niigata 945-1195 JAPAN sh...@ie... TEL(&FAX): +81-257-22-8161 +========================================================+ |
From: Ethan A M. <me...@uw...> - 2025-04-03 05:50:24
|
On Wednesday, 2 April 2025 17:52:48 PDT Shigeharu TAKENO wrote: > shige 04/03 2025 > ---------------- > > Old gnuplot-1.1 is in SouceForge site. I found historical old > gnuplot 1.0 (1.0.3). > > I make the archive file of them (.tar.Z) > > http://takeno.iee.niit.ac.jp/~shige/unix/gnuplot/data/gnuplot-1.0.tar.Z > Very nice code archaeology. Congratulations. I don't have a version of gcc old enough to compile it with without providing a compatibility header and hacking a couple of lines that refer to obsolete error handling, but after that the *.c files compile with only a few complaints! I will add the tarball to the gnuplot-historical directory on SourceForge. It would be nice to also add it to the git repository, but ... When Eric Raymond helped create our current git repository from a combination of the cvs content and historical tarballs of earlier versions he made it so that each of the historical version was present as a tag. I can check each one out by name for inspection. Like this: ========================================================= [~/git/gnuplot-main] git tag 1.1 1.10A 2.0 3.0 3.1 3.2 3.5 3.7.1 3.7.2 3.7.3 ... etc [~/git/gnuplot-main] git checkout --detach 1.1 HEAD is now at 2f87cf77c Content from historic/gnuplot-1.1.tar.gz ========================================================= But I have no idea how to add this version 1.0 snapshot to the repository so that it matches the others. Does anyone know an appropriate set of git commands? > +========================================================+ > Shigeharu TAKENO NIigata Institute of Technology > kashiwazaki,Niigata 945-1195 JAPAN > sh...@ie... TEL(&FAX): +81-257-22-8161 > +========================================================+ -- Ethan A Merritt Department of Biochemistry University of Washington, Seattle |
From: Dima K. <gn...@di...> - 2025-04-04 17:16:37
|
Ethan A Merritt <me...@uw...> writes: > [~/git/gnuplot-main] git checkout --detach 1.1 > HEAD is now at 2f87cf77c Content from historic/gnuplot-1.1.tar.gz > ========================================================= > > But I have no idea how to add this version 1.0 snapshot to the > repository so that it matches the others. Does anyone know an > appropriate set of git commands? If you insert the new 1.0 code into the tree, that will change all the commit IDs downstream of it (i.e. everything we're actively working on now). So I'd add 1.0 by itself in its own root. So 1.1 wouldn't be a child of 1.0, but since this is all for historical archiving, that doesn't really matter. You can do this by - Creating a brand-new repo (let's say in /tmp/gnuplot1), and adding the gnuplot 1.0 code and the "1.0" tag there - In your main gnuplot tree, add this as a remote git remote add gnuplot1 /tmp/gnuplot1 git fetch gnuplot1 Now the "1.0" tag has been ingested into your tree, and if you "git push --tags", you'll send all your tags (including this one) to sourceforge. That's it. To make it easier, I made the gnuplot1 repo, and pushed it here: https://github.com/dkogan/gnuplot1.git so all you need to do is - git remote add gnuplot1 https://github.com/dkogan/gnuplot1.git - git fetch gnuplot1 That's it |
From: Ethan A M. <me...@uw...> - 2025-04-06 21:59:54
|
On Friday, 4 April 2025 09:59:31 PDT Dima Kogan wrote: > > Ethan A Merritt <me...@uw...> writes: > > > [~/git/gnuplot-main] git checkout --detach 1.1 > > HEAD is now at 2f87cf77c Content from historic/gnuplot-1.1.tar.gz > > ========================================================= > > > > But I have no idea how to add this version 1.0 snapshot to the > > repository so that it matches the others. Does anyone know an > > appropriate set of git commands? > > If you insert the new 1.0 code into the tree, that will change all the > commit IDs downstream of it (i.e. everything we're actively working on > now). So I'd add 1.0 by itself in its own root. So 1.1 wouldn't be a > child of 1.0, but since this is all for historical archiving, that > doesn't really matter. > > You can do this by > > - Creating a brand-new repo (let's say in /tmp/gnuplot1), and adding the > gnuplot 1.0 code and the "1.0" tag there > > - In your main gnuplot tree, add this as a remote > > git remote add gnuplot1 /tmp/gnuplot1 > git fetch gnuplot1 > > Now the "1.0" tag has been ingested into your tree, and if you "git push > --tags", you'll send all your tags (including this one) to sourceforge. > That's it. Thanks. I messed up a couple of times but eventually got it. I think. Ethan |
From: Dima K. <gn...@di...> - 2025-04-06 22:11:53
|
> Thanks. I messed up a couple of times but eventually got it. I think. Did you push the tag already (git push --tags)? I don't see it in the main repo. |
From: Ethan A M. <me...@uw...> - 2025-04-07 02:45:54
|
On Sunday, 6 April 2025 15:11:47 PDT Dima Kogan wrote: > Did you push the tag already (git push --tags)? I don't see it in the > main repo. Yeah, I was going to ask you about that. I pushed it. It's there. I can see it on SourceForge. But in order to pull it I need to do "git pull --tags" The extra option isn't needed in other cases, so why now? Ethan |
From: Dima K. <gn...@di...> - 2025-04-07 03:19:45
|
I just read the docs (git fetch --help). I think the key line is By default, any tag that points into the histories being fetched is also fetched; the effect is to fetch tags that point at branches that you are interested in. This default behavior can be changed by using the --tags or --no-tags options I guess the difference here is that the new "1.0" tag is in a separate tree, disconnected from the rest of it, so you need to ask for the tags explicitly. I had no idea this was a thing. In any case, this is probably fine for a historical thing. |