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

Re: Option for git bisect run to automatically clean up

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 29, 2012, 19:24 UTC
Message-ID
<7v4nmgiqej.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAP8UFD21eCSzjJ3a0SxPTzzi2z4KMFr=1xE3j8fPz38AJrrJTQ@mail.gmail.com>
Christian Couder <christian.couder@gmail.com> writes:
Show 5 quoted lines
> I understand that, but I wonder what we should do if some people
> need a "git reset --hard" and if some other people need other
> options than -dfx.
> We would need both a --reset and a --clean, or perhaps even a
> --reset[=(hard|mixed|soft|merge|keep) and a --clean[=<clean-opts>].
Show 5 quoted lines
> And then what if people want to clean only a subdirectory and not
> everything?  And this does not take into account the fact that
> many people will/should clean using "make clean" or "make
> distclean" or "rake clean" or something like that, so that a
> --clean option will not help them.

In short, the users can do that easily in their "run" script, and the definition of "clean-up" will be different depending on what the "run" script does (it may do "make" in which case "make clean" may be a way, it may do "git apply fixup.patch" in which case "git apply -R fixup.patch" may be the way, etc.), so adding "--clean" does not help the users. Just make the "run" script clean after itself.

If that is the argument, I'd buy that.
Previous: Christian Couder
Message 3 of 3 in “Option for git bisect run to automatically clean up”
  1. Laszlo PappSep 27, 2012
  2. Christian CouderSep 29, 2012
  3. Junio C HamanoSep 29, 2012

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.