All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: maximilian attems <max@stro.at>
Cc: Tay Ray Chuan <rctay89@gmail.com>, git@vger.kernel.org
Subject: Re: bug in name-rev on linux-2.6 repo?
Date: Thu, 22 Apr 2010 07:40:43 -0500	[thread overview]
Message-ID: <20100422124042.GA1433@progeny.tock> (raw)
In-Reply-To: <20100422121408.GI3211@stro.at>

Hi maks,

maximilian attems wrote:

> ~/src/linux-2.6$ git name-rev a1de02dccf906faba2ee2d99cac56799bda3b96a
>  a1de02dccf906faba2ee2d99cac56799bda3b96a undefined

Thanks for pointing it out.  This is weird.

The commit doesn’t seem to be part of any tagged release, nor linus’s
master:

| $ git log ^v2.6.34-rc5 ^origin/master a1de02dccf --oneline
| a1de02d ext4: fix async i/o writes beyond 4GB to a sparse file

So maybe it was rewritten; searching for a commit with the same subject:

| $ git log v2.6.33..origin/master --grep='ext4: fix async' --oneline
| a1de02d ext4: fix async i/o writes beyond 4GB to a sparse file

Huh?  Is it included in origin/master or not?

| $ git version
| git version 1.7.1.rc1

Jonathan

  reply	other threads:[~2010-04-22 12:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21 19:58 bug in name-rev on linux-2.6 repo? maximilian attems
2010-04-22 10:54 ` Tay Ray Chuan
2010-04-22 12:14   ` maximilian attems
2010-04-22 12:40     ` Jonathan Nieder [this message]
2010-04-22 14:29       ` Andreas Schwab
2010-04-22 14:44         ` Jeff King
2010-04-22 14:54           ` Jeff King
2010-04-22 15:03             ` Jonathan Nieder
2010-04-22 15:17               ` Jeff King
2010-04-22 16:25                 ` Jonathan Nieder
2010-04-22 18:20                   ` Linus Torvalds
2010-04-24 23:04                     ` tytso
2010-04-22 14:51         ` Jonathan Nieder

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=20100422124042.GA1433@progeny.tock \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=max@stro.at \
    --cc=rctay89@gmail.com \
    /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.