mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@ucw.cz>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Steven Cole <elenstev@mesatop.com>, Greg KH <greg@kroah.com>,
	Greg KH <gregkh@suse.de>, Git Mailing List <git@vger.kernel.org>,
	linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: Re: [GIT PATCH] I2C and W1 bugfixes for 2.6.12-rc2
Date: Wed, 20 Apr 2005 01:02:33 +0200	[thread overview]
Message-ID: <20050419230233.GI9305@pasky.ji.cz> (raw)
In-Reply-To: <Pine.LNX.4.58.0504191525290.2274@ppc970.osdl.org>

Dear diary, on Wed, Apr 20, 2005 at 12:38:17AM CEST, I got a letter
where Linus Torvalds <torvalds@osdl.org> told me that...
> Just say no to patches. 

FYI, I've - per Junio's suggestion - made git merge's fast-forward to
apply show-diff output as a patch instead. This is roughly equal to
doing the sanity check against local changes, except that it handles
them, while at it. (Tree merge refuses to work when there are local
changes.)

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor

  reply	other threads:[~2005-04-19 23:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19  4:39 Greg KH
2005-04-19 18:58 ` Greg KH
2005-04-19 19:40   ` Linus Torvalds
2005-04-19 19:47     ` Greg KH
2005-04-19 20:20       ` Linus Torvalds
2005-04-19 21:40         ` Greg KH
2005-04-19 22:39         ` Petr Baudis
2005-04-19 22:49           ` Linus Torvalds
2005-04-19 22:19     ` Steven Cole
2005-04-19 22:26       ` Petr Baudis
2005-04-19 22:45         ` Junio C Hamano
2005-04-19 22:58           ` Petr Baudis
2005-04-19 22:38       ` Linus Torvalds
2005-04-19 23:02         ` Petr Baudis [this message]
2005-04-19 23:04         ` Steven Cole
2005-04-19 23:16           ` Petr Baudis
2005-04-19 23:38           ` Linus Torvalds
2005-04-19 23:41             ` Steven Cole

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=20050419230233.GI9305@pasky.ji.cz \
    --to=pasky@ucw.cz \
    --cc=elenstev@mesatop.com \
    --cc=git@vger.kernel.org \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sensors@stimpy.netroedge.com \
    --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

all inboxes | Powered by JetHome®