I'm forwarding your comments to the LRDE Projects list, where discussions on Vcs take place.
It's great to see Vcs ran almost out-of-the-box for you! :)
On 3/22/07, Roland Levillain roland@lrde.epita.fr wrote:
I'm forwarding your comments to the LRDE Projects list, where discussions on Vcs take place.
It's great to see Vcs ran almost out-of-the-box for you! :)
---------- Forwarded message ---------- From: "Benoit Perrot" benoit@lrde.epita.fr To: tiger-patches@lrde.epita.fr Date: Tue, 20 Mar 2007 23:49:52 +0100 (CET) Subject: Re: 2547: Move argp/ to lib/argp/. Wow, vcs is pretty cool BUT I wish I had some documentation ;)
I had no problem setting up my environment, but:
- having vcs complaining that I have junk files in my development workspace,
Yep, that's a rule (--force to break it), but you don't want to break it.
$ cat .vcs ---
# excluded files will completely disappear from svn status exclude: # !re is for regular expression - !re .o$ # plain strings - dir/toto - tata
# You will still see them but not as unrecognized files. unmask: - !re .log$
There is also some default conventions: files beginning by: ',' are junk files '+' are precious ...
- having it helping me to actually write my ChangeLog entry (I had already written one, I've been lucky to understand what was happening and not to duplicate my entry :)
Yes, that's an issue for beginners.
- having it diying because I provided a --file=svn-commit.tmp in the first place
The error message could certainly be improved :)
is quite scary, especially when committing in TC :P
I understand your point!
Of course from now on I will let vcs do everything, but migrating from an all-by-hand way to *this* is quite destabilizing -- the first time at least.
Anyway, I very much appreciated its error recovery capability (it failed several times due to my lack of knowledge, but each time in a gracefull manner and conserving my last choices) and its verbosity, even if it does not replace a little manpage ;)
Error recovery is one of the main features of Vcs and that's not only for beginners. Some reasons are: SMTPSERVER not well setup (laptop), wrong passphrase three times, you discovered something missing while reading the patch...
It's verbosity can be reduced by setting .vcs flag:
$ cat ~/.vcs [ .... ] new_user: false # I'm no longer a beginner interactive: true # I still want some y/n questions color: xmas_tree # I like colors
"Nicolas Pouillard" nicolas.pouillard@gmail.com writes:
On 3/22/07, Roland Levillain roland@lrde.epita.fr wrote:
I'm forwarding your comments to the LRDE Projects list, where discussions on Vcs take place.
It's great to see Vcs ran almost out-of-the-box for you! :)
---------- Forwarded message ---------- From: "Benoit Perrot" benoit@lrde.epita.fr To: tiger-patches@lrde.epita.fr Date: Tue, 20 Mar 2007 23:49:52 +0100 (CET) Subject: Re: 2547: Move argp/ to lib/argp/. Wow, vcs is pretty cool BUT I wish I had some documentation ;)
I had no problem setting up my environment, but:
[...]
- having it helping me to actually write my ChangeLog entry (I had already written one, I've been lucky to understand what was happening and not to duplicate my entry :)
Yes, that's an issue for beginners.
Anymway, I'm still missing this feature. Currently, I compose my ChangeLog entry with Emacs while (or after) patching, and I cut-paste it into Vcs' form. I'd like to avoid these unecessary manipulations.
Other than this small issue, Vcs is a useful tool!
Oh, BTW, it seems that Vcs doesn't support the svn's `-c' (`--change') option, probably introduced by version 1.3 or 1.4 :
brasilia ~/src/tc % which svn 18:56 #219 svn: aliased to vcs-svn brasilia ~/src/tc % svn diff -c 2551 src/parse/tiger-parser.cc 18:56 #220 vcs: error: ambiguous option: -c brasilia ~/src/tc % \svn diff -c 2551 src/parse/tiger-parser.cc Err 1 #221 Index: src/parse/tiger-parser.cc =================================================================== --- src/parse/tiger-parser.cc (révision 2550) +++ src/parse/tiger-parser.cc (révision 2551) @@ -42,6 +42,7 @@ return *this; }
+/*<object<-*/ /// Enable object extensions. TigerParser& TigerParser::enable_object_extensions (bool b) @@ -49,6 +50,7 @@ enable_object_extensions_p_ = b; return *this; } +/*->>*/
/// Enable syntax extensions. TigerParser&
On 3/22/07, Roland Levillain roland@lrde.epita.fr wrote:
"Nicolas Pouillard" nicolas.pouillard@gmail.com writes:
On 3/22/07, Roland Levillain roland@lrde.epita.fr wrote:
I'm forwarding your comments to the LRDE Projects list, where discussions on Vcs take place.
It's great to see Vcs ran almost out-of-the-box for you! :)
---------- Forwarded message ---------- From: "Benoit Perrot" benoit@lrde.epita.fr To: tiger-patches@lrde.epita.fr Date: Tue, 20 Mar 2007 23:49:52 +0100 (CET) Subject: Re: 2547: Move argp/ to lib/argp/. Wow, vcs is pretty cool BUT I wish I had some documentation ;)
I had no problem setting up my environment, but:
[...]
- having it helping me to actually write my ChangeLog entry (I had already written one, I've been lucky to understand what was happening and not to duplicate my entry :)
Yes, that's an issue for beginners.
Anymway, I'm still missing this feature. Currently, I compose my ChangeLog entry with Emacs while (or after) patching, and I cut-paste it into Vcs' form. I'd like to avoid these unecessary manipulations.
I remember that, but that's not simple.
Other than this small issue, Vcs is a useful tool!
Oh, BTW, it seems that Vcs doesn't support the svn's `-c' (`--change') option, probably introduced by version 1.3 or 1.4 :
Yep, that's just a matter of adding it to vcs/svn.rb.
It will be in the next version.