it looks like a glibc patch included $Id, so when it was added to cvs, it was rewritten :/. https://sources.gentoo.org/gentoo/src/patchsets/glibc/2.23/00_all_0001-Updated-translations-for-2.23.patch?view=log i tried resetting the keywords with `cvs up -kb`, but that doesn't seem to stick. can someone with admin perms fix this for me ?
ping
Maybe it's time to switch to a maintained VCS?
@vapier: It seems the knowledge to this has been lost by developers. It doesn't require any special admin powers at all, you can fix it yourself, just like you used to do. $ cvs admin -ko 0_all_0001-Updated-translations-for-2.23.patch RCS file: /var/cvsroot/gentoo/src/patchsets/glibc/2.23/00_all_0001-Updated-translations-for-2.23.patch,v done $ cvs status 00_all_0001-Updated-translations-for-2.23.patch =================================================================== File: 00_all_0001-Updated-translations-for-2.23.patch Status: Up-to-date Working revision: 1.3 Repository revision: 1.3 /var/cvsroot/gentoo/src/patchsets/glibc/2.23/00_all_0001-Updated-translations-for-2.23.patch,v Commit Identifier: 739b56ddc1934567 Sticky Tag: (none) Sticky Date: (none) Sticky Options: -ko
Furthermore, can we see about exporting gentoo/src/patchsets/glibc as a repo on it's own?
there's a number of projects in CVS that i'll need to figure out wrt glibc, the patchset dir is not the "upstream" anymore. i migrated to using branches in the upstream glibc git repo years ago with glibc-2.18. but i still need somewhere to commit the contents of the actual patch tarballs.
(In reply to SpanKY from comment #5) > there's a number of projects in CVS that i'll need to figure out > > wrt glibc, the patchset dir is not the "upstream" anymore. i migrated to > using branches in the upstream glibc git repo years ago with glibc-2.18. > but i still need somewhere to commit the contents of the actual patch > tarballs. Discussion for those CVS projects moving to bug #599734.
