From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Olaf Hering <olaf@aepfle.de>
Cc: git@vger.kernel.org
Subject: Re: history damage in linux.git
Date: Thu, 21 Apr 2016 14:51:13 +0200 [thread overview]
Message-ID: <vpqy487unum.fsf@anie.imag.fr> (raw)
In-Reply-To: <20160421123251.GA3186@aepfle.de> (Olaf Hering's message of "Thu, 21 Apr 2016 14:32:51 +0200")
Olaf Hering <olaf@aepfle.de> writes:
> On Thu, Apr 21, Matthieu Moy wrote:
>
>> My guess is that this commit has been sitting for a long time in a
>> repo outside Linus' linux.git, and got merged only recently.
>
> Thats what it looks like. And thats what I'm complaining about. But in
> fact that file is there since v3.13-rc7 (if the tag is really correct in
> my patch file), since at least end of 2014.
Ah, indeed. It was merged right before 3.13. See "git tag --contains
aed06b9cfcab".
It's indeed weird that "git describe --contains" gives a named based on
tag v4.6-rc1, but it is not really incorrect since tags/v4.6-rc1~9^2~792
is indeed a correct name for aed06b9cfcabf8644ac5f6f108c0b3d01522f88b,
and actually uses a tag that follows it.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2016-04-21 12:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 11:30 history damage in linux.git Olaf Hering
2016-04-21 12:10 ` Matthieu Moy
2016-04-21 12:32 ` Olaf Hering
2016-04-21 12:51 ` Matthieu Moy [this message]
2016-04-21 13:19 ` John Keeping
2016-04-21 15:54 ` Olaf Hering
2016-04-21 16:36 ` Matthieu Moy
2016-04-21 13:24 ` Andreas Schwab
2016-04-21 16:36 ` Linus Torvalds
2016-04-21 16:59 ` Junio C Hamano
2016-04-21 17:08 ` Jeff King
2016-04-21 17:23 ` Linus Torvalds
2016-04-21 17:44 ` Stefan Beller
2016-04-21 22:16 ` Junio C Hamano
2016-04-21 18:05 ` Jeff King
2016-04-21 18:18 ` Linus Torvalds
2016-04-22 13:38 ` Johannes Schindelin
2016-04-21 17:00 ` Linus Torvalds
2016-04-21 17:23 ` Junio C Hamano
2016-04-21 17:43 ` Linus Torvalds
2016-04-21 17:59 ` Linus Torvalds
2016-04-21 18:09 ` Jeff King
2016-04-21 19:27 ` Junio C Hamano
2016-04-21 19:43 ` Linus Torvalds
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=vpqy487unum.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=olaf@aepfle.de \
/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.