"george espinoza via GitGitGadget" <gitgitgadget@xxxxxxxxx> writes: > From: george espinoza <gespinoz2019@xxxxxxxxx> > > Signed-off-by: george espinoza <gespinoz2019@xxxxxxxxx> > --- While developing your first patch, it is expected that you make mistake in an earlier step (e.g. 2/6) and then later realize it and want to fix, like this one. Instead of going back to the earlier mistake and fixing it right there before building more on top, tentatively fixing with "oops that was wrong" like this one and building further (i.e. 4 and later steps) is an expedient way. But once you are done, you need to get your act together before presenting the resulting series to the general public. Please learn to use "rebase -i" to clean up the series before asking GGG to publish it to the list. Thanks. > builtin/merge-ours.c | 5 ----- > 1 file changed, 5 deletions(-) > > diff --git a/builtin/merge-ours.c b/builtin/merge-ours.c > index 3980f4899a..4594507420 100644 > --- a/builtin/merge-ours.c > +++ b/builtin/merge-ours.c > @@ -11,11 +11,6 @@ > #include "git-compat-util.h" > #include "builtin.h" > #include "diff.h" > -#include "parse-options.h" > - > -/* parse-options.h added to initiate replacement of manual option parsing > - * with parse-options. > - */ > > static const char builtin_merge_ours_usage[] = > "git merge-ours <base>... -- HEAD <remote>...";
