On Mon, Jun 29, 2015 at 11:21 PM, Liam R. Howlett < liam.howl...@windriver.com> wrote:
> Hello, > > Since git 2.3, there have been a number of new fsck options added which > produce issues when I clone the repository > git://anongit.freedesktop.org/systemd/systemd > > $ git fsck --full > Checking object directories: 100% (256/256), done. > warning in tag 2a440962bc639c674cef95f5dee6f184c5daf170: invalid format > - expected 'tagger' line This is fine, old git versions (until mid-2005) used to create tags without a 'tagger' field and you can find those everywhere including git.git itself. error in tag e1ea4e5f1c429fbe62e76fc5b42bee32c2dcd770: unterminated > header > error in tag f298b6a712bbe700fe1dbac5b81cdc7dd22be26d: unterminated > header > error in tag 4ea98ca6db3b84f5bc16eac8574e5c209ec823ce: unterminated > header > Also seems to be caused by old-format tags – when there was no message, git-tag didn't write the separating empty line either. These new tests are enabled by default when using git fsck. I have been > testing with git version 2.4.4.409.g5b1d901 and thought you might want > to know so the error/warning messages can be corrected. > Not sure if it's worth fixing it, the post-clone fsck does not show such warnings, only a full fsck does. And existing repos wouldn't fetch the updated tags. Though it could be done easily using https://gist.github.com/c66d9ad2cfd1395a97fa or similar scripts. Also note that the primary repository is at https://github.com/systemd/systemd these days. -- Mantas Mikulėnas <graw...@gmail.com>
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel