December 01, 2009
Speaking of improving the VCS usage, how about tagging?

It would be nice if a tag is created for each dmd, phobos and druntime repositories, sometimes I want to see what changed between a version and another and it's not trivial to do so.

I know there is a changelog in the website, but I want to see the actual changes, the diffs, not only a high-level description of the change.

Thanks!

-- 
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
Creativity is great but plagiarism is faster
December 01, 2009
On Tue, 01 Dec 2009 11:16:06 -0500, Leandro Lucarella <llucax@gmail.com> wrote:

> Speaking of improving the VCS usage, how about tagging?
>
> It would be nice if a tag is created for each dmd, phobos and druntime
> repositories, sometimes I want to see what changed between a version and
> another and it's not trivial to do so.
>
> I know there is a changelog in the website, but I want to see the actual
> changes, the diffs, not only a high-level description of the change.
>
> Thanks!
>

Sure is barren, but this is what you are looking for I think:

http://www.dsource.org/projects/druntime/browser/tags
http://www.dsource.org/projects/phobos/browser/tags

Don't know of dmd's source solution, so I don't know where those tags would be.

I agree it would be good if these were kept up to date.  You can probably figure out at least the druntime and phobos tags from history.

-Steve
December 01, 2009
Leandro Lucarella Wrote:

> Speaking of improving the VCS usage, how about tagging?

An easy intermediate step would be to include the SVN revision numbers of Phobos ad Druntime when a release is packaged.  In fact, the makefiles could probably dump this information somewhere and have it built into the libraries, thanks to the mixin file feature.  Maybe I'll add a version string to the Runtime object for this (at least for Druntime).  In Phobos, I guess this could go in std.compiler, though there has to be a better place for it.
December 01, 2009
On Tue, Dec 1, 2009 at 8:45 AM, Steven Schveighoffer <schveiguy@yahoo.com> wrote:
> On Tue, 01 Dec 2009 11:16:06 -0500, Leandro Lucarella <llucax@gmail.com> wrote:
>
>> Speaking of improving the VCS usage, how about tagging?
>>
>> It would be nice if a tag is created for each dmd, phobos and druntime repositories, sometimes I want to see what changed between a version and another and it's not trivial to do so.
>>
>> I know there is a changelog in the website, but I want to see the actual changes, the diffs, not only a high-level description of the change.
>>
>> Thanks!
>>
>
> Sure is barren, but this is what you are looking for I think:
>
> http://www.dsource.org/projects/druntime/browser/tags http://www.dsource.org/projects/phobos/browser/tags
>
> Don't know of dmd's source solution, so I don't know where those tags would be.

http://www.dsource.org/projects/dmd/browser/tags

--bb
December 01, 2009
On Tue, 01 Dec 2009 11:52:32 -0500, Sean Kelly <sean@invisibleduck.org> wrote:

> Leandro Lucarella Wrote:
>
>> Speaking of improving the VCS usage, how about tagging?
>
> An easy intermediate step would be to include the SVN revision numbers of Phobos ad Druntime when a release is packaged.  In fact, the makefiles could probably dump this information somewhere and have it built into the libraries, thanks to the mixin file feature.  Maybe I'll add a version string to the Runtime object for this (at least for Druntime).  In Phobos, I guess this could go in std.compiler, though there has to be a better place for it.

How is this easier than tagging?  Tagging is almost a no-op.

-Steve
December 01, 2009
Bill Baxter, el  1 de diciembre a las 08:53 me escribiste:
> On Tue, Dec 1, 2009 at 8:45 AM, Steven Schveighoffer <schveiguy@yahoo.com> wrote:
> > On Tue, 01 Dec 2009 11:16:06 -0500, Leandro Lucarella <llucax@gmail.com> wrote:
> >
> >> Speaking of improving the VCS usage, how about tagging?
> >>
> >> It would be nice if a tag is created for each dmd, phobos and druntime repositories, sometimes I want to see what changed between a version and another and it's not trivial to do so.
> >>
> >> I know there is a changelog in the website, but I want to see the actual changes, the diffs, not only a high-level description of the change.
> >>
> >> Thanks!
> >>
> >
> > Sure is barren, but this is what you are looking for I think:
> >
> > http://www.dsource.org/projects/druntime/browser/tags http://www.dsource.org/projects/phobos/browser/tags
> >
> > Don't know of dmd's source solution, so I don't know where those tags would be.
> 
> http://www.dsource.org/projects/dmd/browser/tags

I know where they should be, the problem is, nobody creates them! =)

-- 
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
SATANAS EN COMISARIA
	-- Crónica TV
December 01, 2009
Sean Kelly, el  1 de diciembre a las 11:52 me escribiste:
> Leandro Lucarella Wrote:
> 
> > Speaking of improving the VCS usage, how about tagging?
> 
> An easy intermediate step would be to include the SVN revision numbers of Phobos ad Druntime when a release is packaged.  In fact, the makefiles could probably dump this information somewhere and have it built into the libraries, thanks to the mixin file feature.  Maybe I'll add a version string to the Runtime object for this (at least for Druntime).  In Phobos, I guess this could go in std.compiler, though there has to be a better place for it.

I think that would be nice too, but tagging is easy enough, I don't know if you have any release script, but if you do, tagging can be automatically done in that script.

-- 
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
ADOLESCENTE MUERE DESNUCADO POR TRATAR DE AUTOCHUPARSE
	-- Cronista TV
December 01, 2009
On Tue, Dec 1, 2009 at 9:19 AM, Leandro Lucarella <llucax@gmail.com> wrote:
> Sean Kelly, el  1 de diciembre a las 11:52 me escribiste:
>> Leandro Lucarella Wrote:
>>
>> > Speaking of improving the VCS usage, how about tagging?
>>
>> An easy intermediate step would be to include the SVN revision numbers of Phobos ad Druntime when a release is packaged.  In fact, the makefiles could probably dump this information somewhere and have it built into the libraries, thanks to the mixin file feature.  Maybe I'll add a version string to the Runtime object for this (at least for Druntime).  In Phobos, I guess this could go in std.compiler, though there has to be a better place for it.
>
> I think that would be nice too, but tagging is easy enough, I don't know if you have any release script, but if you do, tagging can be automatically done in that script.

Perhaps Walter just doesn't really know what tags are or what they are good for.

So here's the doc for them: http://svnbook.red-bean.com/en/1.1/ch04s06.html

Key example:

  svn copy http://svn.example.com/repos/calc/trunk \
           http://svn.example.com/repos/calc/tags/release-1.0 \
                  -m "Tagging the 1.0 release of the 'calc' project."

(creates the tagged version with tag "release-1.0").

--bb
December 01, 2009
Leandro Lucarella Wrote:

> Sean Kelly, el  1 de diciembre a las 11:52 me escribiste:
> > Leandro Lucarella Wrote:
> > 
> > > Speaking of improving the VCS usage, how about tagging?
> > 
> > An easy intermediate step would be to include the SVN revision numbers of Phobos ad Druntime when a release is packaged.  In fact, the makefiles could probably dump this information somewhere and have it built into the libraries, thanks to the mixin file feature.  Maybe I'll add a version string to the Runtime object for this (at least for Druntime).  In Phobos, I guess this could go in std.compiler, though there has to be a better place for it.
> 
> I think that would be nice too, but tagging is easy enough, I don't know if you have any release script, but if you do, tagging can be automatically done in that script.

Walter does use a release script.  It could probably be modified to tag revisions without too much trouble.
December 01, 2009
Steven Schveighoffer Wrote:

> On Tue, 01 Dec 2009 11:52:32 -0500, Sean Kelly <sean@invisibleduck.org> wrote:
> 
> > Leandro Lucarella Wrote:
> >
> >> Speaking of improving the VCS usage, how about tagging?
> >
> > An easy intermediate step would be to include the SVN revision numbers of Phobos ad Druntime when a release is packaged.  In fact, the makefiles could probably dump this information somewhere and have it built into the libraries, thanks to the mixin file feature.  Maybe I'll add a version string to the Runtime object for this (at least for Druntime).  In Phobos, I guess this could go in std.compiler, though there has to be a better place for it.
> 
> How is this easier than tagging?  Tagging is almost a no-op.

It's easier because it could be built into the Druntime/Phobos makefiles and not rely on a release script or manual effort to actually happen.
« First   ‹ Prev
1 2
Top | Discussion index | About this forum | D home