Re: Git updates (tag renaming and rsync-bpc based on rsync 3.1.2)

Craig Barratt <[email protected]> Sat, 8 Apr 2017 11:18:59 -0700
Newsgroups gmane.comp.sysutils.backup.backuppc.devel
Message-ID <CADSzEFgBS0NsHr5RyX3bXXLn_z7mOJi4i3iwSZ_OvN+YY7hyuw@mail.gmail.com>
--===============7435153773490970247==
Content-Type: multipart/alternative; boundary=001a113ce7b2dcd8ae054cabc757

--001a113ce7b2dcd8ae054cabc757
Content-Type: text/plain; charset=UTF-8

Alexander,

Hmmm, good points.  However, the move to github was only about a year ago
and I doubt many packages have been released based on github releases since
then.

So while there might be a little bit of pain from the changes, no one has
complained (yet).

Craig

On Mon, Apr 3, 2017 at 7:44 AM, Alexander Moisseev <[email protected]>
wrote:

> On 03.04.2017 0:17, Craig Barratt wrote:
>
>> Yesterday I renamed all the tags in backuppc, backuppc-xs and rsync-bpc
>> from "vX_Y_Z" to "X.Y.Z" (eg, v4_1_1 -> 4.1.1).  The reason from way back
>> is that CVS doesn't allow periods in tag names.
>>
>>
> Craig, when I asked about changing tags format to "X.Y.Z", I didn't mean
> changing existing tags.
> I believe changing something (like commits or tags) in a public repository
> is a terrible idea.
> At least this change has made sources unfetchable for current ports.
>
> Would you please rename them back (just commits previously tagged as
> "vX_Y_Z")?
> Or maybe if you like you can use both tags "vX_Y_Z" and "X.Y.Z" for each
> of those commits.
>
> Of course, "X.Y.Z" format for new releases is fine.
>

--001a113ce7b2dcd8ae054cabc757
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Alexander,<div><br></div><div>Hmmm, good points.=C2=A0 How=
ever, the move to github was only about a year ago and I doubt many package=
s have been released based on github releases since then.</div><div><br></d=
iv><div>So while there might be a little bit of pain from the changes, no o=
ne has complained (yet).</div><div><br>Craig</div></div><div class=3D"gmail=
_extra"><br><div class=3D"gmail_quote">On Mon, Apr 3, 2017 at 7:44 AM, Alex=
ander Moisseev <span dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]=
" target=3D"_blank">[email protected]</a>&gt;</span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex"><span class=3D"">On 03.04.2017 0:17, Craig Barratt wr=
ote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Yesterday I renamed all the tags in backuppc, backuppc-xs and rsync-bpc fro=
m &quot;vX_Y_Z&quot; to &quot;X.Y.Z&quot; (eg, v4_1_1 -&gt; 4.1.1).=C2=A0 T=
he reason from way back is that CVS doesn&#39;t allow periods in tag names.=
<br>
<br>
</blockquote>
<br></span>
Craig, when I asked about changing tags format to &quot;X.Y.Z&quot;, I didn=
&#39;t mean changing existing tags.<br>
I believe changing something (like commits or tags) in a public repository =
is a terrible idea.<br>
At least this change has made sources unfetchable for current ports.<br>
<br>
Would you please rename them back (just commits previously tagged as &quot;=
vX_Y_Z&quot;)?<br>
Or maybe if you like you can use both tags &quot;vX_Y_Z&quot; and &quot;X.Y=
.Z&quot; for each of those commits.<br>
<br>
Of course, &quot;X.Y.Z&quot; format for new releases is fine.<br>
</blockquote></div><br></div>

--001a113ce7b2dcd8ae054cabc757--


--===============7435153773490970247==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
--===============7435153773490970247==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
BackupPC-devel mailing list
[email protected]
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

--===============7435153773490970247==--