On 29/03/2011 22.58, Tormod Volden wrote:
On Tue, Mar 29, 2011 at 10:35 PM, Øyvind Harboe wrote:
How about adding a "contribute" script which did the following:
- fetch from origin
- commit changes from user, bringing up a text editor with
a template commit message.
- rebase origin to the master branch, abort if there are conflicts
- create patches and git send-email them to the list
Hi,
I would suggest shipping a HACKING or README.patches file that shows
the "real" commands to do the above steps. Teach a man to fish...
Otherwise I think your "contribute" script will be yet another Easy
Git[1]. And if every little project makes their own "contribute"
implementation, it will just be more confusion for everyone.
Cheers,
Tormod
I agree, sending some patches are not so difficult even for novices.
Basic steps I do are:
1) configure git
git config --global user.name <your name>
git config --global user.email <your e-mail>
git config --global core.editor <your preferred editor, eg. vi>
git config --global sendemail.smtpserver <your smtp server>
git config --global sendemail.smtpserverport <your smtp server port>
git config --global sendemail.smtpuser <your user name>
git config --global sendemail.smtppass <your password>
2) create a develop branch
git checkout -b develop
3)
while (1) {
do some changes
git commit -a -s
git format-patch master..develop
git send-email <patch>
}
4) from time to time:
git checkout master
git pull
git checkout develop
git merge master (or preferably "git rebase master")
Anyway I wonder if there is a better way. Any hints?
regards
Luca
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
