You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by Jacques Le Roux <ja...@les7arts.com> on 2006/10/14 07:52:46 UTC
Subversion allows a file to be updated but not committed ?
Hi,
Someone knows if there is a way in Subversion to allows file(s) to be updated but not committed ?
Thanks
Jacques
Re: Subversion allows a file to be updated but not committed ?
Posted by Illya Kysil <ik...@gmail.com>.
Jacques Le Roux wrote:
> Hi,
>
> Someone knows if there is a way in Subversion to allows file(s) to be
> updated but not committed ?
A classic approach I would recommend is to make a branch and relocate
your working copy (or sub folder) to the branch location. You shall
merge the changes from trunk into your branch until you finish with your
developments. Then you merge the changes from your branch to trunk. You
may commit changes from your branch anytime you want, of course, but
they will not be visible to those who work with trunk.
"Version Control with Subversion" has a nice chapter on branching and
merging. http://svnbook.red-bean.com/
--
Illya Kysil
-----------------------------------------------------------------------------
Shakespeare / King Henry IV
GLENDOWER I can call spirits from the vasty deep.
HOTSPUR Why, so can I, or so can any man;
But will they come when you do call for them?
Re: Subversion allows a file to be updated but not committed ?
Posted by Jacques Le Roux <ja...@les7arts.com>.
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" <yo...@apache.org>
> 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 <ti...@sastau.it> 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
> >
> >
Re: Subversion allows a file to be updated but not committed ?
Posted by Yoav Shapira <yo...@apache.org>.
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 <ti...@sastau.it> 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
>
>
Re: Subversion allows a file to be updated but not committed ?
Posted by Jacopo Cappellato <ti...@sastau.it>.
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
Re: Subversion allows a file to be updated but not committed ?
Posted by Jacques Le Roux <ja...@les7arts.com>.
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
Re: Subversion allows a file to be updated but not committed ?
Posted by Jacopo Cappellato <ti...@sastau.it>.
Hi Jacques,
not sure to understand what you mean, could you please better explain?
svn update will not do any commits...
Jacopo
Not
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