>>good news: tag is there (https://code.djangoproject.com/changeset/17810)
Thanks! >>Out of curiosity, what's the benefit of using an svn tag over the released tarball? For my project I need to apply some patches to the django code (eg for #8280). Applying a patch on svn checkout allows me to track my changes better, and upgrade them between releases. Johan From: django-developers@googlegroups.com [mailto:django-developers@googlegroups.com] On Behalf Of Florian Apolloner Sent: Monday, March 26, 2012 5:48 PM To: django-developers@googlegroups.com Subject: Re: Tagging 1.4 django release in Subversion Hi, good news: tag is there (https://code.djangoproject.com/changeset/17810) On Monday, March 26, 2012 6:05:47 AM UTC+2, Tai Lee wrote: How come? The release that can be downloaded from the site already must correspond to an SVN revision number, right? Why not tag it as such so that people can easily get the same code from SVN as from the release tarball? Out of curiosity, what's the benefit of using an svn tag over the released tarball? Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/dZ-7tRLAXswJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
