-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHnhyr7To545NnTEARAr3gAKD1ikMgB74Qw+65fdZRn0kaEXry8ACcDIva
bEVF2ZqTSaaf5hOE3hmfZyw=
=wRDe
-----END PGP SIGNATURE-----
Hi,
On Mon, Jan 28, 2008 at 01:19:23PM -0500, Theodore Tso wrote:
> 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!!
Done, though it should be doable from your side as well by something
like
git push reporepo :refs/tags/v1.40.5
I believe.
--
Petr "Pasky" Baudis
We don't know who it was that discovered water, but we're pretty sure
that it wasn't a fish. -- Marshall McLuhan
On Tue, Jan 29, 2008 at 01:43:31AM +0100, Petr Baudis wrote:
> Done, though it should be doable from your side as well by something
> like
> git push reporepo :refs/tags/v1.40.5
>
Wow, I thought that only worked on branches, but you're right, that
works. Thanks!!!
- Ted