Revision 6aef46308f48155b43a30764d651e980ca18384f authored by Cody Sehl on 25 October 2016, 21:32:05 UTC, committed by GitHub on 25 October 2016, 21:32:05 UTC
The first few paragraphs in the git-rebase.txt documentation lay out the steps git takes during a rebase: 1. everything from `<upstream>..HEAD` is saved to a temporary area 2. `HEAD` is set to `<upstream>` 3. the changes held in the temporary area are applied one by one in order on top of the new `HEAD` The second step was described using the phrase `The current branch is reset to <upstream>`, which is true (because `HEAD` == current branch), but not clear.
1 parent 6598894
varint.h
#ifndef VARINT_H
#define VARINT_H
extern int encode_varint(uintmax_t, unsigned char *);
extern uintmax_t decode_varint(const unsigned char **);
#endif /* VARINT_H */
Computing file changes ...
