'git format-patch -o ' did an equivalent of ' mkdir ' not ' mkdir -p ', which is being corrected.Īvoid the usage of ' adjust_shared_perm' on the leading directories which may have security implications. (Merged by Junio C Hamano - gitster - in commit f1afbb0, ) format-patch: create leading components of output directory See commit edefc31 () by Bert Wesarg ( bertwesarg). Let's port that similar logic over from patch-id.c into diff.c so we can get the same hash when we're generating patch-ids for ' format-patch -base=' types of command invocations.īefore Git 2.24 (Q4 2019), " git format-patch -o " did an equivalent of " mkdir " not " mkdir -p ", which is being corrected. Generated "stable" patch-ids with the ' patch-id' tool.
#Seagate mac format patch code
Patch-id generation code in diff.c, but we were doing that when we We weren't flushing the context each time we processed a hunk in the (Merged by Junio C Hamano - gitster - in commit 8202d12, ) format-patch: make -base patch-id output stable See commit a8f6855, commit 6f93d26 () by Stephen Boyd ( akshayka). Git 2.23 (Q3 2019) will improve that, because the " -base" option of " format-patch" computed the patch-ids for prerequisite patches in an unstable way, which has been updated to compute in a way that is compatible with " git patch-id -stable".
#Seagate mac format patch Patch
The "base commit" is shown as " base-commit: " followed by the 40-hex ofĪ "prerequisite patch" is shown as " prerequisite-patch-id: " followed by the 40-hex "patch id", which can be obtained by passing the patch through the " git patch-id -stable" command. That need to be applied on top of "base commit" in topological order Well-known patches in flight that is not yet part of the "base commit" The base tree info consists of the "base commit", which is a well-knownĬommit that is part of the stable part of the project history everybodyĮlse works off of, and zero or more "prerequisite patches", which are Message (either the cover letter or the first patch in the series). To record the base tree info and append it at the end of the first Maintainers or third party testers may want to know the exact base tree (Merged by Junio C Hamano - gitster - in commit 72ce3ff, ) format-patch: add ' -base' option to record base tree info See commit bb52995, commit 3de6651, commit fa2ab86, commit ded2c09 () by Xiaolong Ye (``). Git format-patch -M -C COMMIT_VALUE~.COMMIT_VALUE Git format-patch -base=auto -M -C COMMIT_VALUE~.COMMIT_VALUE If you want to be sure the (single commit) patch will be applied on top of a specific commit, you can use the new git 2.9 (June 2016) option git format-patch -base git format-patch -base=COMMIT_VALUE~ -M -C COMMIT_VALUE~.COMMIT_VALUE
0 kommentar(er)
