Questions about Git
ZuLuuuuuu
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.
Luca Bruno
<canol...@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.
Ask everything you want.
Thanks very much.
--
http://lethalman.blogspot.com - Thoughts about computer technologies
http://code.google.com/p/syx - A new Smalltalk implementation
http://www.ammazzatecitutti.org - E adesso ammazzateci tutti
ZuLuuuuuu
> 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.
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.
>
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?
Luca Bruno
Hash: SHA1
> 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.
>
> 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?
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.
- --
http://syx.googlecode.com - Smalltalk YX
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkh95NQACgkQw9Qj+8Kak3EsoACfZ2WVVBOhAiqy9oIEQgLxyH8m
pNMAn1FH+epu9GDSY4kkFrGNq+bw13tr
=JxpI
-----END PGP SIGNATURE-----
ZuLuuuuuu
Luca Bruno
Hash: SHA1
ZuLuuuuuu <canol...@gmail.com> wrote:
>
> Thanks...
>
Forgot to say that if you made a commit:
git diff HEAD^ > my.patch
Will diff the last commit. Instead git diff only is relative to the index.
- --
http://syx.googlecode.com - Smalltalk YX
http://lethalman.blogspot.com - Thoughts about computer technologies
Version: GnuPG v1.4.9 (GNU/Linux)
VOAAn3BY15cgy5ujBchZogXEc8O724B2
=9BYC
-----END PGP SIGNATURE-----