From: Roland McGrath <roland@redhat.com>
To: Jim Meyering <jim@meyering.net>
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: git cvs/ tags
Date: Fri, 15 May 2009 20:17:00 -0000 [thread overview]
Message-ID: <20090515201722.2DBF9FC35D@magilla.sf.frob.com> (raw)
So now we have the git repository. All hail the git repository. Thanks,
Jim! But we have a couple of lingering issues from the CVS conversion.
There was no cvs/<branch> head that corresponded to the last CVS commit.
I made one by hand, called cvs/master.
The head master-UNNAMED-BRANCH existed for some reason, not under cvs/.
It was 7ce88cbdc45a8fb68c5cd1b69d95dee9b11913ee.
I removed it. Is this some abandoned wrong-converted history?
Its log entry matches that for d585b66fa4d11059948f466c9080a6826932358d.
'git describe' can find nothing for either of these commits, which is odd.
d585b66fa4d11059948f466c9080a6826932358d is in the history of
cvs/fedora-2_3-branch.
We have no git tags at all. What happened to our cvs/* migrated tags?
That is a bunch of lost information, including the exact points in history
of various past releases, Fedora builds, etc. What gives?
Thanks,
Roland
next reply other threads:[~2009-05-15 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 20:17 Roland McGrath [this message]
[not found] ` <874ovm6ngw.fsf@meyering.net>
2009-05-15 22:02 ` Roland McGrath
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=20090515201722.2DBF9FC35D@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=jim@meyering.net \
--cc=libc-hacker@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).