public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Greg KH <greg@kroah.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
	"Brown, Len" <len.brown@intel.com>,
	"David S. Miller" <davem@davemloft.net>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	akpm@osdl.org, git@vger.kernel.org
Subject: Re: git pull on Linux/ACPI release tree
Date: Fri, 13 Jan 2006 15:50:27 +0100	[thread overview]
Message-ID: <20060113145027.GN29663@stusta.de> (raw)
In-Reply-To: <20060112013706.GA3339@kroah.com>

On Wed, Jan 11, 2006 at 05:37:06PM -0800, Greg KH wrote:
> On Tue, Jan 10, 2006 at 09:19:09PM +0100, Adrian Bunk wrote:
> > 
> > I am using the workaround of carrying the patches in a mail folder, 
> > applying them in a batch, and not pulling from your tree between 
> > applying a batch of patches and you pulling from my tree.
> 
> Ick, I'd strongly recommend using quilt for this.  It works great for
> just this kind of workflow.

It works in my case because I'm only going through the folder with the 
trivial patches in batches and ask Linus to pull from my tree 
immediately after I'm finished.

That would certainly not be a recommended practice for a subsystem 
maintainer, but I'm handling only trivial patches.

> thanks,
> 
> greg k-h

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2006-01-13 14:50 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-08 18:28 git pull on Linux/ACPI release tree Brown, Len
2006-01-08 19:19 ` Martin Langhoff
2006-01-08 19:33   ` Junio C Hamano
2006-01-08 19:57     ` Linus Torvalds
2006-01-08 20:50       ` Tony Luck
2006-01-08 19:56   ` Linus Torvalds
2006-01-08 20:35     ` David S. Miller
2006-01-08 21:20     ` Luben Tuikov
2006-01-09  1:13       ` Linus Torvalds
2006-01-08 19:41 ` Linus Torvalds
2006-01-08 23:06   ` Adrian Bunk
2006-01-08 23:53     ` Willy Tarreau
2006-01-09  3:26     ` Linus Torvalds
2006-01-09  4:34       ` Martin Langhoff
2006-01-10 20:19       ` Adrian Bunk
2006-01-10 20:31         ` Linus Torvalds
2006-01-10 20:33         ` Martin Langhoff
2006-01-12  1:37         ` Greg KH
2006-01-12 16:10           ` Catalin Marinas
2006-01-13 14:50           ` Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-09  8:05 Brown, Len
2006-01-09 16:47 ` Linus Torvalds
2006-01-09 16:57   ` Linus Torvalds
2006-01-09 22:51     ` Luben Tuikov
2006-01-09 23:07       ` Linus Torvalds
2006-01-09 23:34         ` Martin Langhoff
2006-01-10  2:50       ` Linus Torvalds
2006-01-10  6:33         ` Kyle Moffett
2006-01-10  6:38           ` Martin Langhoff
2006-01-10 18:05             ` Kyle Moffett
2006-01-10 18:27               ` Linus Torvalds
2006-01-10 18:45                 ` Johannes Schindelin
2006-01-10 19:01                   ` Linus Torvalds
2006-01-10 19:28                     ` Linus Torvalds
2006-01-13 23:35                     ` Matthias Urlichs
2006-01-11  3:32               ` Luben Tuikov
2006-01-09 20:06   ` Junio C Hamano
2006-01-10 15:31     ` Alex Riesen
2006-01-09  7:34 Brown, Len
2006-01-09 10:11 ` Martin Langhoff
2006-01-09 12:31   ` Johannes Schindelin
2006-01-09  6:27 Brown, Len
2006-01-09  6:13 Brown, Len
2006-01-09  5:55 linux
2006-01-09  5:53 Brown, Len
2006-01-09  6:08 ` Martin Langhoff
2006-01-09  6:13   ` Linus Torvalds
2006-01-09  6:46     ` Junio C Hamano
2006-01-08  7:47 Brown, Len
2006-01-08  8:16 ` David S. Miller
2006-01-08  8:16 ` Catalin Marinas
2006-01-08 19:10 ` Linus Torvalds
2006-01-09  0:48   ` Al Viro
2006-01-09  3:50     ` Linus Torvalds
2005-12-01  8:05 Len Brown
2005-12-06  8:17 ` Len Brown
2005-12-23  5:42   ` Len Brown
2006-01-07 15:54     ` Len Brown
2006-01-07 18:22       ` Linus Torvalds

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=20060113145027.GN29663@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=git@vger.kernel.org \
    --cc=greg@kroah.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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