After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 405436 - No way to see branch points and "tags" for a file
No way to see branch points and "tags" for a file
Status: RESOLVED OBSOLETE
Product: website
Classification: Infrastructure
Component: svn.gnome.org (obsolete)
current
Other Linux
: Normal normal
: ---
Assigned To: Bonsai Maintainers
Bonsai Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-02-07 17:14 UTC by Shaun McCance
Modified: 2010-04-29 22:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Shaun McCance 2007-02-07 17:14:10 UTC
Compare these two pages:

http://cvs.gnome.org/viewcvs/yelp/src/yelp-db-pager.c?rev=1.62&view=log
http://svn.gnome.org/viewcvs/yelp/trunk/src/yelp-db-pager.c?rev=2560&view=log

With the CVS page, I can tell that revision 1.61 was tagged with YELP_2_15_1 and YELP_2_15_2.  When trying to track down the source of a bug, this is incredibly useful information to have.  With the SVN listing, there's no way to get that information short of manually looking at all the directories under yelp/tags.

I realize that SVN doesn't actually have real tags (a design mistake, IMO).  And I know that, while SVN knows where the tags were copied from, it doesn't know where things were copied to.  So this probably isn't an easy thing to do.

I think this could be accomplished by storing the branch point information in a database on the server.  The database could be updated by a server-side hook or by a cron job.  Then viewcvs could just look up entries in the database when it displays the history of a file.
Comment 1 Shaun McCance 2010-04-29 22:55:14 UTC
Obsolete with git.