netdev - Re: [RFC patch net/next] net: Hoist assigns from if?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100615.104625.179919135.davem@davemloft.net>
Date:	Tue, 15 Jun 2010 10:46:25 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	joe@...ches.com
Cc:	eric.dumazet@...il.com, netdev@...r.kernel.org
Subject: Re: [RFC patch net/next] net: Hoist assigns from if?

From: Joe Perches <joe@...ches.com>
Date: Tue, 15 Jun 2010 10:42:30 -0700

> On Tue, 2010-06-15 at 10:23 -0700, David Miller wrote:
>> > What do you think is missing from the gitk file viewer?
>> I don't use the gitk file viewer, I use "git blame".
> 
> I've never thought git blame was very good for changelog
> tracking as it's a static representation at a particular
> commit/rev.
> 
>> 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.
> 
> You want an interactive, text-based (curses?) git-blame style
> file viewer with push/pop git rev-list capabilities?
> 
> Something akin to emacs egit?

No, I want "git blame" to tell me where a line of code came from,
rather than who the last turkey was who did some coding style
cleanup.

I don't want something interactive, I want a command line I can
type in which gives me the answer.  "git blame" on the surface
can do this, and most of the time it serves my needs, but as soon
as rabid cleanups enter into the picture, the tool becomes useless.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html