Re: .svn folder in each folder after downloading source from svn

[email protected]
Newsgroups gmane.comp.security.ipcop.devel
Message-ID <[email protected]>

----- Mail original -----
> De: "Vinod Nadiadwala" <[email protected]>
> À: "John Edwards" <[email protected]>, "Vinod Nadiadwala" <[email protected]>,
> [email protected]
> Envoyé: Lundi 16 Janvier 2012 15:12:16
> Objet: Re: [IPCop-devel] .svn folder in each folder after downloading source from svn
> 
> 
> i understand that .svn folder is to share your customization, but
> what if it is not successful, what is procedure to stop sharing at
> SVN because i am not sure about what i am doing, and will it be
> successful or not ? so i want to know it will be shared after
> confirmation of it's success then it's ok, but if it directly
> uploades the changes directly to svn then it will be problematic to
> other users, please explain,
> (i don't want to report my changes to svn, without confirmation)
> 
> 
You don't have commit right on SF repository so you can't broke the tree for the others that way.
It should appear to you convenient to keep your changes on svn tree if you pull the current tree.
Once your changes are made, you could list them with 'svn diff' and create a patch.
svn diff >../mychanges.patch
Then you could publish your patch that other could apply with patch -i ../mychanges.patch

You still could pull upstream changes with 'svn up' (hoping that does not conflict with your changes).

Gilles

------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
IPCop-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ipcop-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.