James Livingston wrote:
G'day everyone,
Since I originally asked about this on #arch, I discovered that whatever
was causing the problem seems to have been fixed in 1.2.1. I've still
got a couple of question that I can't find an answer to on the web, or
in the the list archives.
Originally a couple of us who are hacking on Rhythmbox were having
issues with recent versions from one of the RB branches. After figuring
out which patch was causing the problem I sat down and tried to
determine what was going wrong.
A sort time ago (after I asked on #arch) I noticed that the column of
the tla output which reports what was done to the file (M=modified,
C=conflict, etc) was giving "?M" for two of the files touched by this
particular patch when using tla 1.2.0, but the normal "M" on any later
version.
I can't find any description of what "?M" means, but the results were
that those particular files didn't get modified - yet tla didn't report
any error and continued applying later patches.
Could anyone tell me what the "?M" means, and why it would fail to apply
the patch successfully yet continue without any error?
Cheers,
James "Doc" Livingston
Did the file in question have a space in the name?
I believe "?M" is a statement saying that there was a modification, but
it couldn't find the file associated with it.
Often this is actually okay. Say you created a branch from me, and
created some new files for your purpose. I can merge your changes to my
files, without worrying about the changes to files I don't have.
I believe the changes actually go in a directory named ++patches-missing.
Anyway, tla before 1.2 something didn't handle spaces in filenames, so
it is possible that it just can't find the file.
John
=:->
signature.asc
Description: OpenPGP digital signature
_______________________________________________
Gnu-arch-users mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnu-arch-users
GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/
