Re: [Sugar-devel] Fwd: making patches and sending email using git-email
On Sat, Oct 2, 2010 at 10:50, Sascha Silbe sascha-ml-reply-to-201...@silbe.org wrote: Excerpts from Ishan Bansal's message of Fri Oct 01 19:58:23 +0200 2010: 2. To do the git email configuration for your system refer to http://paste.ubuntu.com/488777/ Could we improve what we have in the wiki and refer people there? I would add some more recommendations: 1. Introduce yourself to the community. 2. Don't leave questions without a reply. 3. Whenever you take a task that someone else was doing, mention it explicitly so others aren't concerned about wasting efforts. 4. Ask when you don't understand. 5. Answer other people's questions when you can. Regards, Tomeu From there: 17 git send-email --to sugar-devel@lists.sugarlabs.org patchname.patch FWIW, you don't need to create the patch (using format-patch) first, git-send-email can do that for you: git send-email HEAD^..HEAD You can configure the destination address so you don't need to specify it manually every time: git config sendemail.to sugar-devel sugar-devel@lists.sugarlabs.org You need to do this for each of the repositories you are working on (e.g. sugar + sugar-toolkit). Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fwd: making patches and sending email using git-email
On Tue, Oct 5, 2010 at 11:09, Tomeu Vizoso to...@sugarlabs.org wrote: On Sat, Oct 2, 2010 at 10:50, Sascha Silbe sascha-ml-reply-to-201...@silbe.org wrote: Excerpts from Ishan Bansal's message of Fri Oct 01 19:58:23 +0200 2010: 2. To do the git email configuration for your system refer to http://paste.ubuntu.com/488777/ Could we improve what we have in the wiki and refer people there? I would add some more recommendations: 1. Introduce yourself to the community. 2. Don't leave questions without a reply. 3. Whenever you take a task that someone else was doing, mention it explicitly so others aren't concerned about wasting efforts. 4. Ask when you don't understand. 5. Answer other people's questions when you can. Just one more :) 6. Don't take things off-list unless it's a personal matter. Well, the last: 7. Read all messages sent to the mailing list. Regards, Tomeu Regards, Tomeu From there: 17 git send-email --to sugar-devel@lists.sugarlabs.org patchname.patch FWIW, you don't need to create the patch (using format-patch) first, git-send-email can do that for you: git send-email HEAD^..HEAD You can configure the destination address so you don't need to specify it manually every time: git config sendemail.to sugar-devel sugar-devel@lists.sugarlabs.org You need to do this for each of the repositories you are working on (e.g. sugar + sugar-toolkit). Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fwd: making patches and sending email using git-email
On Tue, Oct 5, 2010 at 5:09 AM, Tomeu Vizoso to...@sugarlabs.org wrote: On Sat, Oct 2, 2010 at 10:50, Sascha Silbe sascha-ml-reply-to-201...@silbe.org wrote: Excerpts from Ishan Bansal's message of Fri Oct 01 19:58:23 +0200 2010: 2. To do the git email configuration for your system refer to http://paste.ubuntu.com/488777/ Could we improve what we have in the wiki and refer people there? I've expanded http://wiki.sugarlabs.org/go/Activity_Team/Git_FAQ#How_do_I_send_a_patch_to_the_Sugar_developers.3F to incorporate this and Sascha's amendments. I would add some more recommendations: 1. Introduce yourself to the community. 2. Don't leave questions without a reply. 3. Whenever you take a task that someone else was doing, mention it explicitly so others aren't concerned about wasting efforts. 4. Ask when you don't understand. 5. Answer other people's questions when you can. Good idea. -walter Regards, Tomeu From there: 17 git send-email --to sugar-devel@lists.sugarlabs.org patchname.patch FWIW, you don't need to create the patch (using format-patch) first, git-send-email can do that for you: git send-email HEAD^..HEAD You can configure the destination address so you don't need to specify it manually every time: git config sendemail.to sugar-devel sugar-devel@lists.sugarlabs.org You need to do this for each of the repositories you are working on (e.g. sugar + sugar-toolkit). Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fwd: making patches and sending email using git-email
Excerpts from Ishan Bansal's message of Fri Oct 01 19:58:23 +0200 2010: 2. To do the git email configuration for your system refer to http://paste.ubuntu.com/488777/ From there: 17 git send-email --to sugar-devel@lists.sugarlabs.org patchname.patch FWIW, you don't need to create the patch (using format-patch) first, git-send-email can do that for you: git send-email HEAD^..HEAD You can configure the destination address so you don't need to specify it manually every time: git config sendemail.to sugar-devel sugar-devel@lists.sugarlabs.org You need to do this for each of the repositories you are working on (e.g. sugar + sugar-toolkit). Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Fwd: making patches and sending email using git-email
Team Important steps to be completed before making and sending patches- 1. Do remember to keep the system updated as there are some packages which might not be installed and later on will create problems. 2. To do the git email configuration for your system refer to http://paste.ubuntu.com/488777/ After setting up git-email do send a test mail to any of the members to check for its working. 3. Before making a patch always use command git diff. It would show you the changes which you have made. This would give you a idea on whether there are any undesired changes present since the same thing is reflected in the patch. 4. Once you send the patch at sugar-devel be quick in responding to the suggestions and changes suggested by developers. Remember to add the correct patch version to the email while sending through git send-email. For eg git send-email --annotate --to ishanseeta.in 0001-Specified-bundle-id-for-read-activity-Ticket-2170.patch can be run to edit the message being sent to sugar-devel For the correct way to do add patch version refer to http://lists.sugarlabs.org/archive/sugar-devel/2010-September/026978.html. Regards ishan ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
