Re: Unicode update of width and other character properties

[Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>]

On 2017-12-03 07:07, Thomas Wolff wrote:
>> On Aug 17 07:53, Thomas Wolff wrote:
>> So why don't you use git send-email (ideally with a cover letter, see `git
>> format-patch --cover-letter') instead of attaching the patches to a single
>> email?  This is the correct way of sending patch series and it gets you
>> around the size limit.
> Because of:
> LC_ALL=C git send-email
> git: 'send-email' is not a git command. See 'git --help'.

You need to install git-email, and if you run X you might also want git-gui.

Ensure $GIT_EDITOR|$VISUAL|$EDITOR stays in foreground so that you can edit
commit messages, emails, interactive rebases, merges, etc. e.g.:
	git config --global core.editor 'gvim -f'

You should not need LC_ALL=C most places these days, except to get sort, join,
uniq to play well together.

> Are there any working instructions for newlib contributions to be found
> anywhere?

Everyone assumes you are comfortable with git and understand its model.
Advice I git:

cd  .../repo

git checkout master
git pull
git checkout -b BRANCH

$VISUAL FILE
git add FILE
git commit FILE
...

git format-patch -o PATH/ --stat --cover-letter -#commits
$VISUAL PATH/0000-*cover-letter.patch
git send-email --compose PATH/000?-*.patch

Update branch to the latest upstream master:

git checkout master
git pull
git rebase [-i] master BRANCH

...

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada