|
View:
New views
10 Messages
—
Rating Filter:
Alert me
|
|
|
arch-tag problem?Hey everyone,
Is there any particular reason why tla will not recognise the following line as a correct arch-tag? <?php /* arch-tag: 17B24542-9529-4E47-A1FB-4F799D873AAF */ ?> If I change it to read: <!-- arch-tag: 17B24542-9529-4E47-A1FB-4F799D873AAF --> Everything works fine. (But then the arch-tag shows up in my HTML, which I'd like to avoid...) Did I stumble upon a bug or is this a Feature I Do Not Understand? :) hellfish:~/work/2007/vdms/apps/backend/modules/country aderuwe$ tla -- version The GNU Arch Revision Control System (tla) 1.3.5 tla--atai--1.3--patch-72, built on Feb 10 2007 on MacOS X 10.4.8 Alexander Deruwe _______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@... http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/ |
|
|
Re: arch-tag problem?Unlike a year or so ago, I can't off the top of my head, point you
at the particular lines of code to consider (which, anyway, I'd hesitate to modify for this issue, if I were you, because of interop issues) -- but -- the essence of the answer is that I made the assumption, somewhere along the line, that in any sane comment syntax you could deal with only allowing leading punctuation and whitespace before the tag. You might play around with something like: <?php this comment contains a revision control tag, do NOT alter the next line ...arch-tag: yadda yadda ?> Regards, -t Alexander Deruwe wrote: > Hey everyone, > > Is there any particular reason why tla will not recognise the > following line as a correct arch-tag? > > <?php /* arch-tag: 17B24542-9529-4E47-A1FB-4F799D873AAF */ ?> > > If I change it to read: > > <!-- arch-tag: 17B24542-9529-4E47-A1FB-4F799D873AAF --> > > Everything works fine. (But then the arch-tag shows up in my HTML, > which I'd like to avoid...) > Did I stumble upon a bug or is this a Feature I Do Not Understand? :) > > > hellfish:~/work/2007/vdms/apps/backend/modules/country aderuwe$ tla > --version > The GNU Arch Revision Control System (tla) 1.3.5 > tla--atai--1.3--patch-72, built on Feb 10 2007 > > on MacOS X 10.4.8 > > > Alexander Deruwe > > > _______________________________________________ > Gnu-arch-users mailing list > Gnu-arch-users@... > http://lists.gnu.org/mailman/listinfo/gnu-arch-users > > GNU arch home page: > http://savannah.gnu.org/projects/gnu-arch/ > _______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@... http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/ |
|
|
Re: arch-tag problem?Alexander Deruwe <aderuwe@...> writes:
> <?php /* arch-tag: 17B24542-9529-4E47-A1FB-4F799D873AAF */ ?> > > If I change it to read: > > <!-- arch-tag: 17B24542-9529-4E47-A1FB-4F799D873AAF --> > > Everything works fine. (But then the arch-tag shows up in my HTML, > which I'd like to avoid...) > Did I stumble upon a bug or is this a Feature I Do Not Understand? :) One issue might be that tla does not know about your file's comment syntax, and considers the contents of the arch-tag: to extend to the _end of the line_. Whitespace at the end of the line is stripped off, but other whitespace is not (and if you tags inadvertently include comment end markers, that includes whitespace between the intended tag and the comment end). Thus in the above examples, the tags are: "17B24542-9529-4E47-A1FB-4F799D873AAF */ ?>" and "17B24542-9529-4E47-A1FB-4F799D873AAF -->" In cases where a file uses a bracket-like comment syntax, it's usually a good idea to put comment ending on a new line to avoid problems. E.g. In C, I use tags like: /* arch-tag: 23c5f366-a5ee-44b7-a3b7-90d6da7fd749 (do not change this comment) */ However if you already have a bunch of files that inadvertently include comment end-markers in their tags, you might be stuck, and have to maintain them ... If you're trying to change the above PHP tag to HTML syntax, I guess you could do something like: <!-- arch-tag: 17B24542-9529-4E47-A1FB-4F799D873AAF */ ?> (do not change this comment) --> [Yuck!] A long time ago there was discussion of a new tag syntax (with a new name, probably "arch-id:") which would avoid these issues by using a quoted string for the actual tag contents, e.g.: /* arch-id: "23c5f366-a5ee-44b7-a3b7-90d6da7fd749" */ Would just include the stuff in between quotes in the tag. That never happened though, and given arch's state, it seems kind of unlikely to happen in the future. -Miles -- Quidquid latine dictum sit, altum viditur. _______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@... http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/ |
|
|
Re: Re: arch-tag problem?Miles Bader wrote:
> > given arch's state, What a difficult issue. Personally, I am led to the conclusion that I behaved unethically in soliciting volunteer aid the ways that I did -- and that helped evoke equally (I would even stick my neck out and say worse) unethical behavior by others when money entered the picture via Canonical. (I don't exactly apologize, mind you.... I didn't make those mistakes on purpose and a strive to survive is sometimes impossible to escape with clean hands.) The popular conceptions of how free software projects should work, growing organically out of the once awesome GNU (sw development) project, are simply wrong when confronted with micro-economics at scale. One (very informal) economics mentor put to me as "I think your approach there is, at root, selfish" (paraphrased). So, I'm reluctant to fire up the ESR social manipulation techniques to do much about the public GNU Arch project at the moment .... YET.... in spite of the wins of Darcs and bazaar and so forth.... I do still have some concern that it is far from impossible to do an Arch 2.0 very well and, also, that some of the most valuable lessons from Arch are not well reflected in the most popular competitors that beat it to death in the market. Hrmm. Someone needs to find the intersection of understanding the beast and a viable free software business model. Its a bit tricky in the current climate. -t _______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@... http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/ |
|
|
Re: Re: arch-tag problem?Stop whining about the past, and finish arch 2.x. You promised if I
recall... _______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@... http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/ |
|
|
Re: Re: arch-tag problem?Alfred M. Szmidt wrote:
> Stop whining about the past, and finish arch 2.x. You promised if I > recall... > > "Promise" is *slightly to strong a term but, yes, I haven't stopped work on it. The message to which you reply was not, by any reasonable definition, "whining." -t _______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@... http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/ |
|
|
Re: Re: arch-tag problem?Anyway, Tom never promised a concrete time frame. So let's give Tom as much time as he needs for Arch 2.0.
I am willing to offer an award. Which will complete first, the Hurd kernel (the next major version) or Arch 2.0. Whatever finishes first, its author will get US$100 from me. Not much money, but a small amount that I can give... On 2/27/07, Thomas Lord <
lord@...> wrote: Alfred M. Szmidt wrote: -- Andy Tai, atai@... _______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@... http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/ |
|
|
Re: Re: arch-tag problem?
Andy Tai wrote:
:-). I dunno, man... you know, arguably, there have been Hurd releases that are already of at least a high a quality and with at least as much promise as the original Linux kernel. What do you mean by "finishes?" You might already owe someone $100 ... or, equally plausibly, might not ever owe either party such a sum :-) -t
_______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@... http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/ |
|
|
Re: arch-tag problem?On 25 Feb 2007, at 04:52, Miles Bader wrote:
> /* arch-tag: 23c5f366-a5ee-44b7-a3b7-90d6da7fd749 > (do not change this comment) */ Of course! I even remember this now from way back! Right. Changed all my tags to look sortof like that, depending on language and see no more problem now. > However if you already have a bunch of files that inadvertently > include > comment end-markers in their tags, you might be stuck, and have to > maintain them ... If you're trying to change the above PHP tag to > HTML syntax, I guess you could do something like: No, I was (am) refreshing everything I knew about arch before importing my current project. :) Haven't needed real revision control in a while, as I was tied to SourceSafe in my previous job. :-P Thanks for the pointer! Alexander Deruwe _______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@... http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/ |
|
|
Re: Re: arch-tag problem? I am willing to offer an award. Which will complete first, the
Hurd kernel (the next major version) or Arch 2.0. Whatever finishes first, its author will get US$100 from me. Not much money, but a small amount that I can give... A Hurd release would not require much work, just label it and you're done. The Hurd has always been very stable. It is this other thing that isn't... _______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@... http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/ |
| Free embeddable forum powered by Nabble | Forum Help |