[nem-en] Re: [nem-feedback] Visual Studio 2005 VSIP package
Kamil Skalski
kamil.skalski at gmail.com
Sat Feb 11 13:28:11 CET 2006
Well, in general it depends on what tools you have installed on your
machine. I will describe a few scenarios, maybe it will be useful for
somebody:
- assuming you have Tortoise SVN installed and source code you changed
is a checkout of svn repository:
1. explore into directory of program in Windows
2. right click on it and choose TortoiseSVN -> Create Patch
3. choose files you changed
4. choose file name for patch
5. send us this new file
- assuming you have cygwin and subversion installed and source code
you changed is a checkout of svn repository:
1. enter into directory of program in cygwin
2. type 'svn diff > mypatch.patch'
3. send us a 'mypatch.patch' file created there
- assuming you don't have a checkout of repository (your case, since
the VS repository is not yet public), but have cygwin:
1. put original sources in directory 'original'
2. put changed sources in directory 'changed'
3. enter into their parent directory
4. type 'diff -uwBr original changed > mypatch.patch'
5. send us 'mypatch.patch' file created there
- assuming you don't have cygwin
1. Download some diff tool like (I didn't try them):
http://www.prestosoft.com/examdiff/examdiffpro.htm
http://www.codeproject.com/tools/rgdiff.asp
http://www.codeproject.com/tools/difftool.asp
2. put original sources in directory 'original'
3. put changed sources in directory 'changed'
4. enter into their parent directory
5. use the diff tool to create a patch, if possible choosing 'unified'
kind of patch
(I hope you are not performing the last scenario, since I didn't ever
try it ;) )
06-02-11, NoiseEHC <NoiseEHC at freemail.hu> napisał(a):
> Oh and something else:
>
> I will send you the latest version tomorrow and you could put it to the
> repository
> but I ask you to write some step by step tutorial of creating a patch
> since I do not
> have the slightest idea about doing that. Suppose that you are writing
> that for
> a complete idiot... :)
>
>
> >> NoiseEHC, what is a status of your work? Is it ok to put the new
> >> source into the repository?
> >>
>
> _______________________________________________
> https://nemerle.org/mailman/listinfo/devel-en
>
--
Kamil Skalski
http://nazgul.omega.pl
More information about the devel-en
mailing list