All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Mark Brown <broonie@kernel.org>
Cc: Peter Foley <pefoley2@pefoley.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-doc@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH 1/4] Documentation: use subdir-y to avoid unnecessary built-in.o files
Date: Sun, 07 Sep 2014 13:52:04 -0700	[thread overview]
Message-ID: <540CC574.4080203@infradead.org> (raw)
In-Reply-To: <20140907184837.GD4015@sirena.org.uk>

On 09/07/14 11:48, Mark Brown wrote:
> On Sun, Sep 07, 2014 at 10:59:53AM -0700, Randy Dunlap wrote:
> 
>> The quilt-import.log from 20140829 says:
> 
>> $ git am --patch-format=mbox ../quilt/rd-docs/001-docum-use-subdiry-avoid-builtin.patch
> 
>> and in the 20140905 git tree it says:
> 
>> $ git am ../quilt/rd-docs/001-docum-use-subdiry-avoid-builtin.patch
>> Patch format detection failed.
> 
>> Are you using Stephen's scripts?  Why would his tree apply patches with
>> --patch-format=mbox
>> while the later trees did not use that git-am option?
> 
> Yes, I'm using his scripts.  I guess it's possible there's something in
> his global git configuration that changes the behaviour?

I can't find any such animal.  Hopefully Stephen can provide some insight
into this.

thanks,
-- 
~Randy

  reply	other threads:[~2014-09-07 20:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-17 14:11 [PATCH 1/4] Documentation: use subdir-y to avoid unnecessary built-in.o files Peter Foley
2014-04-17 14:11 ` [PATCH 2/4] Documentation: add makefiles for more targets Peter Foley
2014-08-26 16:50   ` Andrey Wagin
2014-04-17 14:11 ` [PATCH 3/4] Documentation: make functions static to avoid prototype warnings Peter Foley
2014-04-17 14:11 ` [PATCH 4/4] Documentation: fix misc. warnings Peter Foley
2014-06-29  2:23 ` [PATCH 1/4] Documentation: use subdir-y to avoid unnecessary built-in.o files Randy Dunlap
2014-07-09 20:52   ` Sam Ravnborg
2014-08-25 20:33 ` Randy Dunlap
2014-09-02 22:58   ` Peter Foley
2014-09-02 23:24     ` Randy Dunlap
2014-09-02 23:29       ` Mark Brown
2014-09-03 23:08         ` Peter Foley
2014-09-03 23:21           ` Mark Brown
2014-09-03 23:38             ` Randy Dunlap
2014-09-03 23:49               ` Mark Brown
2014-09-04 10:42               ` Mark Brown
2014-09-06  0:07                 ` Randy Dunlap
2014-09-07 17:59                   ` Randy Dunlap
2014-09-07 18:48                     ` Mark Brown
2014-09-07 20:52                       ` Randy Dunlap [this message]
2014-09-08  8:03                       ` Stephen Rothwell
2014-09-08 10:22                         ` Mark Brown
2014-09-08 14:57                           ` Stephen Rothwell

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=540CC574.4080203@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=broonie@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pefoley2@pefoley.com \
    --cc=sam@ravnborg.org \
    --cc=sfr@canb.auug.org.au \
    /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.