From: Junio C Hamano <gitster@pobox.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Git Mailinglist <git@vger.kernel.org>
Subject: Re: [RFC PATCH v2] Teach rebase to rebase even if upstream is up to date
Date: Sat, 14 Feb 2009 11:56:58 -0800 [thread overview]
Message-ID: <7vr620ssfp.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <bd6139dc0902140957pa5852d6m61211054b3f5e395@mail.gmail.com> (Sverre Rabbelier's message of "Sat, 14 Feb 2009 18:57:28 +0100")
Sverre Rabbelier <srabbelier@gmail.com> writes:
> 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.
prev parent reply other threads:[~2009-02-14 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 22:48 [RFC PATCH v2] Teach rebase to rebase even if upstream is up to date Sverre Rabbelier
2009-02-14 6:07 ` Johannes Schindelin
2009-02-14 17:57 ` Sverre Rabbelier
2009-02-14 19:56 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vr620ssfp.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=srabbelier@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.