I am an amateur programmer. I'd like to contribute to the project but
I didn't contributed to a project before and I have some problems with
using Git.
So far; I installed Git, cloned Syx repository, made some changes in
Integer.st and did the commit. But I cannot create the .patch file.
When I use "git format-patch" command, it creates a patch file
including some additional information about email settings. But I
don't use email client to import the patch file. I just want to attach
a .patch file and send it to this group (or wherever appropriate). I
looked at some old patch emails and the .patch attachments does not
include any information about email settings like "from" "in-reply-to"
etc. at the beginning of the .patch file. How can I prepare such
patches? And where would be more appropriate to send these patches?
I have some more questions but let's ask them after solving this.
In data 15 luglio 2008 alle ore 23:32:35, ZuLuuuuuu <canol.go...@gmail.com> ha scritto:
> Hello,
> I am an amateur programmer. I'd like to contribute to the project
Hello, I'm glad of this.
> but > I didn't contributed to a project before and I have some problems with > using Git.
Oh I'm sorry I knew choosing git could bring problems, but as you will see it's a very fast and stable VCS and the hosting is reliable.
> So far; I installed Git, cloned Syx repository, made some changes in > Integer.st and did the commit. But I cannot create the .patch file. > When I use "git format-patch" command, it creates a patch file > including some additional information about email settings. But I > don't use email client to import the patch file. I just want to attach > a .patch file and send it to this group (or wherever appropriate). > I > looked at some old patch emails and the .patch attachments does not > include any information about email settings like "from" "in-reply-to" > etc. at the beginning of the .patch file. How can I prepare such > patches?
No problem, you can attach straight the formatted patch, I'll do a git apply without any problems. If you still don't want those headers, use git diff.
> And where would be more appropriate to send these patches?
You can send them here or, if you think is more appropriate feel free to open an issue and attach your patch.
> I have some more questions but let's ask them after solving this.
On Jul 16, 12:40 am, "Luca Bruno" <lethalma...@gmail.com> wrote:
> Oh I'm sorry I knew choosing git could bring problems,
> but as you will see it's a very fast and stable VCS and the hosting is
> reliable.
Actually, I didn't use a version control system before, so most
probably Git is a good choice :) I was be able to do the basic steps
on tutorial without a problem.
> No problem, you can attach straight the formatted patch, I'll do a git
> apply without any problems.
> If you still don't want those headers, use git diff.
Thanks.
After typing diff command I should copy paste the output from
terminal, right? I couldn't find a flag to automatically create
a .patch file like "git format-patch" command.
> Ask everything you want.
Ok, here is one another question:
If I change a .c file, I will want to compile Syx and see the results.
But if I do this in the local master branch folder, it will produce a
lot of extra files which shouldn't be in the remote Git repository,
for example the updated makefile, object files, plug-in folders etc. I
can avoid this by copying the master branch folder into somewhere else
whenever I make a change and doing the compilation there. But this
time, even for simple changes in .st files (which does not require
compilation process) I should copy paste that folder. Is there a way
to organize the development structure in my computer so that my trials
won't disturb the Git repository folder I will use to do commits?
> After typing diff command I should copy paste the output from
> terminal, right? I couldn't find a flag to automatically create
> a .patch file like "git format-patch" command.
git diff > filename.patch
> Ok, here is one another question:
> If I change a .c file, I will want to compile Syx and see the results.
> But if I do this in the local master branch folder, it will produce a
> lot of extra files which shouldn't be in the remote Git repository,
> for example the updated makefile, object files, plug-in folders etc. I
> can avoid this by copying the master branch folder into somewhere else
> whenever I make a change and doing the compilation there. But this
> time, even for simple changes in .st files (which does not require
> compilation process) I should copy paste that folder. Is there a way
> to organize the development structure in my computer so that my trials
> won't disturb the Git repository folder I will use to do commits?
No problems with generated files, they won't change anything of the original sources.
Anyway there're local branches:
git checkout -b mybranch
...do everything you want
To switch to master again git checkout master.
To clean everything except original sources git clean -df.
> > After typing diff command I should copy paste the output from
> > terminal, right? I couldn't find a flag to automatically create
> > a .patch file like "git format-patch" command.
> git diff > filename.patch
> > Ok, here is one another question:
> > If I change a .c file, I will want to compile Syx and see the results.
> > But if I do this in the local master branch folder, it will produce a
> > lot of extra files which shouldn't be in the remote Git repository,
> > for example the updated makefile, object files, plug-in folders etc. I
> > can avoid this by copying the master branch folder into somewhere else
> > whenever I make a change and doing the compilation there. But this
> > time, even for simple changes in .st files (which does not require
> > compilation process) I should copy paste that folder. Is there a way
> > to organize the development structure in my computer so that my trials
> > won't disturb the Git repository folder I will use to do commits?
> No problems with generated files, they won't change anything of the original sources.
> Anyway there're local branches:
> git checkout -b mybranch
> ...do everything you want
> To switch to master again git checkout master.
> To clean everything except original sources git clean -df.
