mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@ucw.cz>
Cc: Steven Cole <elenstev@mesatop.com>,
	Linus Torvalds <torvalds@osdl.org>, 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: Tue, 19 Apr 2005 15:45:02 -0700	[thread overview]
Message-ID: <7vpswqpes1.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050419222609.GE9305@pasky.ji.cz> (Petr Baudis's message of "Wed, 20 Apr 2005 00:26:10 +0200")

>>>>> "PB" == Petr Baudis <pasky@ucw.cz> writes:

PB> I'm wondering if doing

PB> if [ "$(show-diff)" ]; then
PB> 	git diff | git apply
PB> else
PB> 	checkout-cache -f -a
PB> fi

PB> would actually buy us some time; or, how common is it for people to have
PB> no local changes whatsoever, and whether relative slowdown of additional
PB> show-diff to git diff would actually matter.

"show-diff -s" perhaps.  Also wouldn't it be faster to pipe
show-diff output (not git diff output) to patch (not git apply)?



  reply	other threads:[~2005-04-19 22:45 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 [this message]
2005-04-19 22:58           ` Petr Baudis
2005-04-19 22:38       ` Linus Torvalds
2005-04-19 23:02         ` Petr Baudis
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=7vpswqpes1.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=elenstev@mesatop.com \
    --cc=git@vger.kernel.org \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pasky@ucw.cz \
    --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®