openembedded-core.git/scripts/create-pull-request, branch jethro

create-pull-request: cleanup bashisms

2015-08-16T08:23:27+00:00

Made create-pull-request POSIX compatible:
   - Replaced /bin/bash -> /bin/sh in shebang.
   - Replaced usage of pushd/popd with generic shell commands.
   - Tested on zsh and dash.

Signed-off-by: Ed Bartosh 
Signed-off-by: Ross Burton

create-pull-request: cd to relative directory

2015-08-09T07:12:45+00:00

create-pull-request -d path creates empty patches if directory
is specified as a path, i.e. ./bitbake or ./bitbake/ or full path.
It behaves expected way only if script is run with -d bitbake, i.e.
relative dir name doesn't contain '\'.

Fixed this unwanted behaviour by changing directory and running
git format-patch in it with --relative, without specifying
relative path as a parameter.

Signed-off-by: Ed Bartosh 
Signed-off-by: Richard Purdie

create-pull-request: Implement -d option

2015-07-31T14:35:34+00:00

This options allows to generate patches against relative directory by
using git format-patch --relative option.
See more details about --relative option in git diff manual page.

For example generating bitbake patchsets from poky can be
done this way: create-pull-request -u contrib -d ./bitbake

Signed-off-by: Ed Bartosh 
Signed-off-by: Ross Burton

Revert "create-pull-request: Fix error on 2.0 versions of git"

2015-07-21T22:52:49+00:00

This breaks create-pull-request for git <2, which is many people.

This reverts commit 7ee64ea60ede5477b2f9a355d93bdc556e6b7895.

Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie

create-pull-request: Fix error on 2.0 versions of git

2015-07-16T14:08:43+00:00

On 2.0 versions of git, the create-pull-request script exits with the
warning "No match for commit... Are you sure you pushed 'HEAD' there?".

This is due to a change in behavior where git used to guess the branch
you meant, but no longer does.  See the thread at
http://www.spinics.net/lists/git/msg233050.html for more information.

To accommodate the new behavior, if the COMMIT_ID is set to the default
of "HEAD", make it point explicitly to $BRANCH instead.

Signed-off-by: Ben Shelton 
Signed-off-by: Ross Burton

create-pull-request: fix git GIT_VERSION

2015-03-09T16:00:21+00:00

If the git version is 1.7.9.5, then 1795 is bigger than 210 which causes
errors like:
fatal: No such ref: :rbt/bash
fatal: Needed a single revision
ERROR: git request-pull reported an error

Use the first 3 numbers to fix the problem.

Signed-off-by: Robert Yang 
Signed-off-by: Ross Burton

create-pull-request: Fix git request-pull

2015-02-07T13:30:57+00:00

Signed-off-by: Saul Wold

create-pull-request: Error message on missing -u

2013-02-08T14:46:02+00:00

The script was erroring out without a hint on what failed.

Signed-off-by: Bernhard Reutner-Fischer 
Signed-off-by: Saul Wold

create-pull-request: detect trailing white space

2012-12-13T14:28:40+00:00

Add logic in the create-pull-request to detect and warn about the
trailing white space inserted by patches.

Signed-off-by: Nitin A Kamble 
Signed-off-by: Saul Wold

create-pull-request: Assume remote branch from local branch

2012-04-10T07:20:47+00:00

It is common to use the same remote branch name as the local branch
name. In this case, it would be nice not to have to specify the
remote branch name.

Make the -b argument optional and assume the remote branch is the same
name as the local branch. Print a NOTE to this effect so as not to
catch the user by surprise:

NOTE: Assuming remote branch 'notthere', use -b to override.

If the remote branch doesn't exist, a WARNING is displayed just as if
the user had used -b to specify a non-existent branch:

WARNING: Branch 'notthere' was not found on the contrib git tree.
         Please check your remote and branch parameter before sending.

Signed-off-by: Darren Hart