summaryrefslogtreecommitdiffstats
path: root/package/python-numpy/Config.in
diff options
context:
space:
mode:
authorWaldemar Brodkorb <wbx@openadk.org>2014-04-29 21:30:27 +0200
committerThomas Petazzoni <thomas.petazzoni@free-electrons.com>2014-07-15 23:40:07 +0200
commitb41ec531c2be1b57712cf1c7402842348cd5b5b5 (patch)
tree118af8b66ea2efe8edf92973f43a2fb9b960e1fe /package/python-numpy/Config.in
parent95c914fae8ff20dac278aea9ae0d74595bf03b88 (diff)
downloadbuildroot-b41ec531c2be1b57712cf1c7402842348cd5b5b5.tar.gz
buildroot-b41ec531c2be1b57712cf1c7402842348cd5b5b5.zip
give a hint about git rebase
It seems common knowledge to use git rebase in interactive mode to fixup issues while respinning patch series, but I found it hard to find any hint about it. Add a note for git beginners like me. [Thomas: take into account Arnout's comment.] Signed-off-by: Waldemar Brodkorb <wbx@openadk.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Diffstat (limited to 'package/python-numpy/Config.in')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud