git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 3/6] This file wasn't supposed to change during my git push for check-ref-format :(

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 7, 2019, 10:23 UTC
Message-ID
<xmqqo8xoouht.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<078a19e86af6fcf1348d8988dc10cfac2e689ba4.1573114201.git.gitgitgadget@gmail.com>
"george espinoza via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: george espinoza <gespinoz2019@gmail.com>
>
> Signed-off-by: george espinoza <gespinoz2019@gmail.com>
> ---

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.
Show 19 quoted lines
>  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>...";
Previous: george espinoza via GitGitGadgetNext: george espinoza via GitGitGadget
Message 10 of 11 in “[Outreachy] check-ref-format: parse-options”
  1. 0/6 [Outreachy] check-ref-format: parse-optionsGeorge Espinoza via GitGitGadget, Nov 7, 2019
  2. 2/6 [Outreachy] check-ref-format: parse-optionsgeorge espinoza via GitGitGadget, Nov 7, 2019
  3. Junio C HamanoNov 7, 2019
  4. George EspinozaNov 9, 2019
  5. 1/6 [Outreachy] merge-ours: include parse-option.hgeorge espinoza via GitGitGadget, Nov 7, 2019
  6. Junio C HamanoNov 7, 2019
  7. 5/6 [Outreachy] check-ref-format: parse-optionsgeorge espinoza via GitGitGadget, Nov 7, 2019
  8. 6/6 [Outreachy] check-ref-format: parse-optionsgeorge espinoza via GitGitGadget, Nov 7, 2019
  9. 3/6 This file wasn't supposed to change during my git push for check-ref-format :(george espinoza via GitGitGadget, Nov 7, 2019
  10. Junio C HamanoNov 7, 2019
  11. 4/6 [Outreachy] check-ref-format: parse optionsgeorge espinoza via GitGitGadget, Nov 7, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.