On Fri, 8 Feb 2008, Simon Holm Th�gersen wrote:
> fre, 08 02 2008 kl. 12:06 -0600, skrev Paul Jackson:
> > 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?
>
On Fri, 8 Feb 2008, Simon Holm Th�gersen wrote:
fre, 08 02 2008 kl. 12:06 -0600, skrev Paul Jackson:
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
Thanks, Olof and Harvey.
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=
Just what I was looking for.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[EMAIL PROTECTED]>
fre, 08 02 2008 kl. 12:06 -0600, skrev Paul Jackson:
> 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
On Fri, Feb 08, 2008 at 12:21:54PM -0600, Olof Johansson wrote:
> On Fri, Feb 08, 2008 at 12:06:23PM -0600, Paul Jackson wrote:
> > 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
On Fri, 2008-02-08 at 12:06 -0600, Paul Jackson wrote:
> 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
On Fri, Feb 08, 2008 at 12:06:23PM -0600, Paul Jackson wrote:
> 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
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
Thanks, Olof and Harvey.
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=
Just what I was looking for.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson [EMAIL PROTECTED]
fre, 08 02 2008 kl. 12:06 -0600, skrev Paul Jackson:
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
On Fri, Feb 08, 2008 at 12:21:54PM -0600, Olof Johansson wrote:
On Fri, Feb 08, 2008 at 12:06:23PM -0600, Paul Jackson wrote:
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
On Fri, Feb 08, 2008 at 12:06:23PM -0600, Paul Jackson wrote:
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
On Fri, 2008-02-08 at 12:06 -0600, Paul Jackson wrote:
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.
On Fri, 8 Feb 2008, Paul Mackerras wrote:
>
> From: Tony Breeds <[EMAIL PROTECTED]>
>
> Commit ad7f71674ad7c3c4467e48f6ab9e85516dae2720 corrected the clock
> ..
Please, when mentioning hex numbers, also do the one-liner shortlog.
I realize that in gitk (or even just with two terminal windows
From: Tony Breeds <[EMAIL PROTECTED]>
Commit ad7f71674ad7c3c4467e48f6ab9e85516dae2720 corrected the clock
resolution reported by the VDSO clock_getres() but introduced another
problem in that older versions of gcc (gcc-4.0 and earlier) fail to
compile the new code in
On Fri, 8 Feb 2008, Paul Mackerras wrote:
From: Tony Breeds [EMAIL PROTECTED]
Commit ad7f71674ad7c3c4467e48f6ab9e85516dae2720 corrected the clock
..
Please, when mentioning hex numbers, also do the one-liner shortlog.
I realize that in gitk (or even just with two terminal windows open
From: Tony Breeds [EMAIL PROTECTED]
Commit ad7f71674ad7c3c4467e48f6ab9e85516dae2720 corrected the clock
resolution reported by the VDSO clock_getres() but introduced another
problem in that older versions of gcc (gcc-4.0 and earlier) fail to
compile the new code in
17 matches
Mail list logo