From: Theodore Tso <tytso@MIT.EDU>
To: linux-ext4@vger.kernel.org
Cc: pasky@suse.cz
Subject: Oops, incorrect tag: v1.40.5 in e2fsprogs git repository
Date: Mon, 28 Jan 2008 13:18:25 -0500 [thread overview]
Message-ID: <20080128181825.GA24206@mit.edu> (raw)
Hi,
I screwed up, and incorrectly tagged v1.40.5 in the e2fsprogs git
repository. I accidentally tagged the "next" branch instead of the
"maint" branch, so the the wrong commit was tagged as v1.40.5. Argh...
This has been fixed on git.kernel.org, but it's still busted on
repo.or.cz.
If you've pulled from the e2fsprogs git repository incorrectly, you'll
need to run the command:
git tag -d v1.40.5
... and then re-pull from the git repository to get the correct tag.
Petr, if you could run the same command on the e2fsprogs repository on
repo.or.cz, it would be much appreciated!!
- Ted
next reply other threads:[~2008-01-28 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 18:18 Theodore Tso [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-28 18:19 Oops, incorrect tag: v1.40.5 in e2fsprogs git repository Theodore Tso
2008-01-29 0:43 ` Petr Baudis
2008-01-29 0:55 ` Theodore Tso
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=20080128181825.GA24206@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=pasky@suse.cz \
/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 NNTP newsgroup(s).