projects / buildroot.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 95c914f) | patch
give a hint about git rebase
authorWaldemar Brodkorb <wbx@openadk.org>
Tue, 29 Apr 2014 19:30:27 +0000 (21:30 +0200)
committerThomas Petazzoni <thomas.petazzoni@free-electrons.com>
Tue, 15 Jul 2014 21:40:07 +0000 (23:40 +0200)
commitb41ec531c2be1b57712cf1c7402842348cd5b5b5
tree118af8b66ea2efe8edf92973f43a2fb9b960e1fetree
parent95c914fae8ff20dac278aea9ae0d74595bf03b88commit | diff
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>
docs/manual/contribute.txt diff | blob | history