Re: Trial git repo is back up

[sfeam <sf...@us...>]

On Wednesday, 18 October 2017 02:12:51 Mojca Miklavec wrote:
> 17. okt. 2017 09:01 "Eric S. Raymond" wrote:
> 
> I see
> 
> esr@snark:/mnt/vault/esr-vault/gnuplot/gnuplot$ git tag --list
> BETA_347_980925
> BETA_347_981005
> BETA_347_98101301
> BETA_347_981121
> BETA_348
> BETA_348_981204
> BETA_349
> BETA_349_990114
> GNUPLOT_19991210
> GNUPLOT_20000330
> GNUPLOT_37_20000507
> GNUPLOT_990311
> GNUPLOT_990312
> GNUPLOT_990404
> GNUPLOT_990507
> GNUPLOT_990602
> GNUPLOT_990612
> GNUPLOT_990705
> GNUPLOT_RELEASE_19991103
> GNUPLOT_RELEASE_3_7_1
> GNUPLOT_RELEASE_3_7_2
> GNUPLOT_RELEASE_3_7_3
> Release_4_2_1
> Release_4_2_1-pre1
> Release_4_2_3
> Release_4_2_4
> Release_4_2_5
> Release_4_2_6
> Release_4_4_0
> Release_4_4_1
> Release_4_4_2
> Release_4_4_3
> Release_4_4_4
> Release_4_4_rc1
> Release_4_6_0
> Release_4_6_1
> Release_4_6_2
> Release_4_6_4
> Release_4_6_5
> Release_4_6_6
> Release_4_6_rc1
> Release_5_0_0
> Release_5_0_1
> Release_5_0_2
> Release_5_0_3
> Release_5_0_4
> Release_5_0_5
> Release_5_0_6
> Release_5_0_7
> Release_5_2_0
> Release_5_2_1
> axis-checkpoint-sourceforge-20000728
> git-conversion
> gnuplot-3-8f
> gnuplot-4-4-alpha
> gnuplot-4-6-alpha
> gnuplot-5-0-rc2
> gnuplot-5-2-rc0
> pm3d-14
> pre-lt-palette
> pre-macport
> pre-pm3d-02
> pre-pm3d-11
> 
> 
> I would suggest unifying those names (perhaps to something like v5.2.rc0),
> but that can be done later.

???
Sorry, I don't get it.
Why would you want to unify any of those?
What I want is to be able to check them out separately.

Everything labeled pre* or BETA* can be junked, but that is
not what I understand as "unify".

Now maybe I just misunderstand the whole git thing.
Remember I'm new to this and thinking in terms of CVS.
What I'm thinking is that if I do 
 git checkout Release_5_0_7

I'll get the same files that were in the release tarball
gnuplot-5.0.7.tar.gz
And if for some reason we wanted to continue development of the 5.0 series
for a release 5.0.8, I could clone it (I don't know what git command that is)
as a new branch Release_5_0_8 and push that one back to the repository.
Have I got that wrong?

	Ethan