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

Re: [RFC PATCH v2] Teach rebase to rebase even if upstream is up to date

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 14, 2009, 19:56 UTC
Message-ID
<7vr620ssfp.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<bd6139dc0902140957pa5852d6m61211054b3f5e395@mail.gmail.com>
Sverre Rabbelier <srabbelier@gmail.com> writes:
Show 16 quoted lines
> On Sat, Feb 14, 2009 at 07:07, Johannes Schindelin
> <Johannes.Schindelin@gmx.de> wrote:
>> I know that you can turn it off with --whitespace=nowarn, but that's
>> such an outlier that we do not have to care about it, right?
>
> Well, actually, in the v1 thread Junio mentioned that it should not
> imply -f for --whitespace=nowarn.
>
>> Or if we really want to:
>>
>>        --whitespace=nowarn) ;;
>>        --whitespace=*) force_rebase=t ;;
>>
>> Hm?
>
> No strong opinion on my side, what does the gitster have to say about it?

"Fix" is obviously a request to "fix" things. On the other hand, at least to me, "warn" is more about "*if you were to* rewrite and find issues, please notify me". So I prefer what is queued already.

Previous: Sverre Rabbelier
Message 4 of 4 in “Teach rebase to rebase even if upstream is up to date”
  1. Teach rebase to rebase even if upstream is up to dateSverre Rabbelier, Feb 13, 2009
  2. Johannes SchindelinFeb 14, 2009
  3. Sverre RabbelierFeb 14, 2009
  4. Junio C HamanoFeb 14, 2009

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.