From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: joe@perches.com, netdev@vger.kernel.org
Subject: Re: [RFC patch net/next] net: Hoist assigns from if?
Date: Tue, 15 Jun 2010 20:04:20 +0200 [thread overview]
Message-ID: <1276625060.2541.166.camel@edumazet-laptop> (raw)
In-Reply-To: <20100615.102305.28825768.davem@davemloft.net>
Le mardi 15 juin 2010 à 10:23 -0700, David Miller a écrit :
> From: Joe Perches <joe@perches.com>
> Date: Tue, 15 Jun 2010 09:22:12 -0700
>
> > On Mon, 2010-06-14 at 22:59 -0700, David Miller wrote:
> >> But that to me just means that until git has a friendlier way to
> >> walk backwards through blame information for a line to skip past
> >> the cleanup crapola, we shouldn't make a lot of these kinds of
> >> changes.
> >
> > What do you think is missing from the gitk file viewer?
>
> I don't use the gitk file viewer, I use "git blame".
>
> Requiring a GUI to get at the information I need is unacceptable. I
> often work remotely and use text consoles for everything, even email
> and web browsing.
>
Same for me, I am very old school, and use a text editor I co-wrote in
1986 ;)
I just tried gitk, but ... where is 'git blame' information ?
Ah let me see : select *one* line and ask
'run git gui blame on this line'.
-> Error on sterr (text console) :
git: 'gui' is not a git command. See 'git --help'.
Did you mean one of these?
grep
init
pull
push
Hmm ?
git --version
git version 1.7.0.4
Oh well...
next prev parent reply other threads:[~2010-06-15 18:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 0:20 [RFC patch net/next] net: Hoist assigns from if? Joe Perches
2010-06-15 5:42 ` Eric Dumazet
2010-06-15 5:59 ` David Miller
2010-06-15 16:22 ` Joe Perches
2010-06-15 17:23 ` David Miller
2010-06-15 17:42 ` Joe Perches
2010-06-15 17:46 ` David Miller
2010-06-15 17:51 ` Joe Perches
2010-06-15 18:04 ` Eric Dumazet [this message]
2010-06-15 18:28 ` Joe Perches
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=1276625060.2541.166.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=netdev@vger.kernel.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