All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
	paulus@samba.org, akpm@linux-foundation.org, tglx@linutronix.de
Subject: Re: [PATCH] Fix compilation of powerpc asm-offsets.c with old gcc
Date: Fri, 8 Feb 2008 12:06:23 -0600	[thread overview]
Message-ID: <20080208120623.3ad74e3a.pj@sgi.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0802071449240.2896@woody.linux-foundation.org>

Linus wrote:
> Please, when mentioning hex numbers, also do the one-liner shortlog.
> ...
> without _requiring_ people to be git users to get the gist of the 
> matter, ok?


Thanks for sticking up for us git-challenged contributors.

Can anyone point me at instructions providing the shortest
path for getting from one of those git hex numbers to the
log or change it represents, for non-git users?

Or do those instructions begin with a first step of:

  1. become a git user
  2. ...

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.940.382.4214

WARNING: multiple messages have this Message-ID (diff)
From: Paul Jackson <pj@sgi.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: paulus@samba.org, akpm@linux-foundation.org, tglx@linutronix.de,
	linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
	tony@bakeyournoodle.com
Subject: Re: [PATCH] Fix compilation of powerpc asm-offsets.c with old gcc
Date: Fri, 8 Feb 2008 12:06:23 -0600	[thread overview]
Message-ID: <20080208120623.3ad74e3a.pj@sgi.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0802071449240.2896@woody.linux-foundation.org>

Linus wrote:
> Please, when mentioning hex numbers, also do the one-liner shortlog.
> ...
> without _requiring_ people to be git users to get the gist of the 
> matter, ok?


Thanks for sticking up for us git-challenged contributors.

Can anyone point me at instructions providing the shortest
path for getting from one of those git hex numbers to the
log or change it represents, for non-git users?

Or do those instructions begin with a first step of:

  1. become a git user
  2. ...

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.940.382.4214

  reply	other threads:[~2008-02-08 18:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07 22:24 [PATCH] Fix compilation of powerpc asm-offsets.c with old gcc Paul Mackerras
2008-02-07 22:24 ` Paul Mackerras
2008-02-07 22:53 ` Linus Torvalds
2008-02-07 22:53   ` Linus Torvalds
2008-02-08 18:06   ` Paul Jackson [this message]
2008-02-08 18:06     ` Paul Jackson
2008-02-08 18:20     ` Harvey Harrison
2008-02-08 18:20       ` Harvey Harrison
2008-02-08 18:21     ` Olof Johansson
2008-02-08 18:21       ` Olof Johansson
2008-02-08 18:23       ` Olof Johansson
2008-02-08 18:39         ` Paul Jackson
2008-02-08 18:31     ` Simon Holm Thøgersen
2008-02-08 18:31       ` Simon Holm Thøgersen
2008-02-11 10:36       ` Geert Uytterhoeven
2008-02-11 10:36         ` Geert Uytterhoeven

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=20080208120623.3ad74e3a.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.