Thanx *charlesmanning*

On Monday, March 10, 2014 4:15:25 AM UTC+5:30, charlesmanning wrote:
>
> You should not generate .diff files because it is hard to know the context 
> and that throws away some useful info.
>
> It is better to use "git format-patch" which sets up the diff as a proper 
> patch, with the commit message and everything. That is far more useful to 
> people trying to understand your patch.
>
> You can then email it to the list you are interested in. The best way to 
> do this is with:
>
> git send-email
>
>
>
>
> On Mon, Mar 10, 2014 at 11:24 AM, Nemina Amarasinghe 
> <nem...@gmail.com<javascript:>
> > wrote:
>
>> Hi,
>>
>> My name is Nemina Amarasinghe, I am a third year computer engineering 
>> student form university of Peradeniya Sri Lanka. I would like to 
>> participate to GSoC'14 under the GIT organization.
>> As the Gsoc page mentioned currently I have cloned and build the git 
>> source code. And now I'm working with one of micro-projects you have 
>> mentioned.
>>
>>
>> *I want to submit the .diff file I have created. Should I attach it in a 
>> email or should I have to submit it somewhere else. *
>> if anyone could give me a answer deeply appreciated
>>
>> Best regards,
>> Nemina Amarasinghe
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Git for human beings" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to git-users+...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to