From: Junio C Hamano <gitster@pobox.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
James Morris <jmorris@namei.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: linux-next: unneeded merge in the security tree
Date: Tue, 12 Mar 2013 20:17:27 -0700 [thread overview]
Message-ID: <7v38w056pk.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130313023026.GD16919@thunk.org> (Theodore Ts'o's message of "Tue, 12 Mar 2013 22:30:26 -0400")
Theodore Ts'o <tytso@mit.edu> writes:
> On Tue, Mar 12, 2013 at 02:30:04PM -0700, Junio C Hamano wrote:
>> Theodore Ts'o <tytso@mit.edu> writes:
>>
>> > [remote "origin"]
>> > url = git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
>> > fetch = +refs/heads/master:refs/heads/master
>> > mergeoptions = --ff-only
>> >
>>
>> Is there an escape hatch for that rare case? IOW, how does a
>> submaintainer who configured the above to override --ff-only?
>
> Hmm, maybe we would need to add a --no-ff-only? Or they could just
> do:
>
> git fetch origin
> git merge FETCH_HEAD
Hmm, neither feel quite nice.
I haven't heard any comments on my alternative proposal, by the
way. Did the message get lost?
next prev parent reply other threads:[~2013-03-13 3:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130312100950.e45ef0e721492ff0d5fd7c8d@canb.auug.org.au>
[not found] ` <alpine.LRH.2.02.1303121510270.25612@tundra.namei.org>
[not found] ` <20130312041641.GE18595@thunk.org>
2013-03-12 17:13 ` linux-next: unneeded merge in the security tree Linus Torvalds
2013-03-12 17:51 ` Geert Uytterhoeven
2013-03-12 19:49 ` Junio C Hamano
2013-03-12 20:02 ` Junio C Hamano
2013-03-12 21:20 ` Theodore Ts'o
2013-03-12 21:28 ` Linus Torvalds
2013-03-12 21:47 ` Junio C Hamano
2013-03-12 21:54 ` Linus Torvalds
2013-03-12 22:00 ` Junio C Hamano
2013-03-13 2:30 ` Theodore Ts'o
2013-03-13 3:17 ` Junio C Hamano [this message]
2013-03-12 21:30 ` Junio C Hamano
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=7v38w056pk.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).