From: Sam Ravnborg <sam@ravnborg.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Greg KH <gregkh@suse.de>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net, git@vger.kernel.org
Subject: Re: [GIT PATCH] USB patches for 2.6.17
Date: Thu, 22 Jun 2006 22:01:47 +0200 [thread overview]
Message-ID: <20060622200147.GA10712@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0606221239100.5498@g5.osdl.org>
> I'm just constantly surprised by how people don't even seem to realize
> what it can do sometimes. Part of it is that development has been pretty
> active (and some of the things it can do simply weren't there three months
> ago), but part of it must be because people don't even expect it to be
> able to do something like that.
Personally I'm still missing two things:
1) A command to let me see what this Linus guy have applied compared to
my tree - without touching anything in my tree. bk changes -R
2) A dry-run of a fetch+pull. I can do that if I really study the man
pages I know. But "git pull --dry-run" would be more convinient.
Other than that I will say that I'm pleased with the funtionality that
I use - that's maybe 10% of the possibilities...
Sam
next prev parent reply other threads:[~2006-06-22 20:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 22:06 Greg KH
2006-06-21 22:22 ` Linus Torvalds
2006-06-21 22:51 ` Greg KH
2006-06-22 0:51 ` Linus Torvalds
2006-06-22 1:22 ` Linus Torvalds
2006-06-22 18:18 ` Greg KH
2006-06-22 18:30 ` Greg KH
2006-06-22 18:49 ` Randy.Dunlap
2006-06-22 18:54 ` Greg KH
2006-06-23 5:52 ` Evgeniy Polyakov
2006-06-23 6:07 ` Greg KH
2006-06-22 19:50 ` Linus Torvalds
2006-06-22 20:01 ` Sam Ravnborg [this message]
2006-06-22 20:52 ` Petr Baudis
2006-06-22 21:01 ` Linus Torvalds
2006-06-22 21:07 ` Linus Torvalds
2006-06-22 23:11 ` Linus Torvalds
2006-06-22 23:40 ` Greg KH
2006-06-22 23:48 ` Linus Torvalds
2006-06-22 23:52 ` Greg KH
2006-06-23 0:32 ` Andrew Morton
2006-06-23 0:41 ` Greg KH
2006-06-23 0:05 ` Jeremy Fitzhardinge
2006-06-23 0:17 ` Andrew Morton
2006-06-23 0:22 ` Greg KH
2006-06-23 0:38 ` Greg KH
2006-06-23 0:56 ` Greg KH
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=20060622200147.GA10712@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@osdl.org \
--cc=git@vger.kernel.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--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
Powered by JetHome