[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7v38w056pk.fsf@alter.siamese.dyndns.org>
Date: Tue, 12 Mar 2013 20:17:27 -0700
From: Junio C Hamano <gitster@...ox.com>
To: Theodore Ts'o <tytso@....edu>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
James Morris <jmorris@...ei.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Git Mailing List <git@...r.kernel.org>
Subject: Re: linux-next: unneeded merge in the security tree
Theodore Ts'o <tytso@....edu> writes:
> On Tue, Mar 12, 2013 at 02:30:04PM -0700, Junio C Hamano wrote:
>> Theodore Ts'o <tytso@....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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists