2009/9/21 Gavin Baumanis <gavinb_at_thespidernet.com>
> Hi Everyone,
>
> This is one of those silly questions... you know the kind... where you
> probably should just know the answer - but don't.
>
> So in the vain of; "There is no such thing as a silly question" here
> it is.
>
> I have a file;
> /trunk/myFile.a
>
> It is currently undergoing significant development.
> One of those developments has been approved for release.
> Normally, we only do a small change or so per file and then create a
> new tag for release from HEAD.
>
> The sticking point for me is;
> The change that is approved - is at r1200. The repo currently sits at
> r1500 - with a significant number of changes made to File.a in between
> 1200 and HEAD.
> (Which is the bit that is odd for me - in that I have never dealt with
> that scenario before.)
>
> I could make a release tag_at_1200
> But then that locks all files to be of no greater a revision that 1200.
>
> I suppose I could simply do a diff of 1200:1199 for /trunk/File.a and
> obtain a unidiff.
> Make a copy of the current release tag. - Which is another problem -
> because we actually don't have a tag per release we just have a
> forever ongoing branch that we use for production uploads.
> And apply the new patch - then commit the new release tag?
> Which seems reasonable enough to me... - but that isn't necessarily
> saying a lot!
>
> And while I realise there could be any number of ways to deal with the
> scenario... is there a generally accepted one? - Along the lines of -
> just about everyone uses trunk / branches and tags a being the
> "accepted" general layout for a repository?
>
> I'd rather not get into a bad habit - if there was indeed a "better"
> way to do it.
>
>
> As always - Thanks for all your help.
> Gavin.
>
> ------------------------------------------------------
>
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2397177
>
> To unsubscribe from this discussion, e-mail: [
> users-unsubscribe_at_subversion.tigris.org].
>
why not just go with a mixed revision working copy of trunk
svn co svn://___/trunk
svn update -r 1200 somefile.ext
and then create the tag from your working copy
svn cp . svn://___/tags/foobar-1.0 -m "release of foobar-1.0 with
approved changes to somefile.ext"
-Stephen
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2397251
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-21 11:39:34 CEST