Yoav, This exactly what I need. I always wondered why export/import was good for. Now I know.
Thanks a bunch ! Jacques From: "Yoav Shapira" <[EMAIL PROTECTED]> > Hi, > svn export will copy a file (or set of files) as-is from svn to a > directory of your choice. It's not a live checkout, so you can't > commit back. If you type svn commit in that directory, nothing will > happen. To update it, rerun the svn export command (you can't run svn > update on it). Otherwise, export and checkout are identical in that > they take the same arguments and options. > > Yoav > > On 10/14/06, Jacopo Cappellato <[EMAIL PROTECTED]> wrote: > > Hi Jacques, > > > > ah, I see what you mean.... but I'm sorry I don't have an answer for this. > > > > Jacopo > > > > PS: I got your mail but when I try to reply to your mail box the message > > is rejected... > > > > > > > > > > Jacques Le Roux wrote: > > > Hi Jacopo, > > > > > > I just want to be able to modify some files (properties, build.xml, etc.) > > > and let them be updated but be sure that I will not commit > > > them by accident, one way only style. > > > I think there is not a such scheme in svn. Would be helpful when you want > > > to keep things simply. > > > Some sort of ignore-commit (but can be updated) > > > > > > Illya, I don't want to make a branch for (in this case) 2 files (but > > > crucial ones). > > > > > > Thanks to both of you > > > > > > Jacques > > > > > >> Hi Jacques, > > >> > > >> not sure to understand what you mean, could you please better explain? > > >> svn update will not do any commits... > > >> > > >> Jacopo > > >> > > >> Jacques Le Roux wrote: > > >>> Hi, > > >>> > > >>> Someone knows if there is a way in Subversion to allows file(s) to be > > >>> updated but not committed ? > > >>> > > >>> Thanks > > >>> > > >>> Jacques > > > >
