I tried to update my Gem copy of Vcs with this one:
http://www.lrde.epita.fr/~pouill_n/vcs/vcs-0.5.2.3.gem
but I got:
brasilia ~/download/software/ruby/vcs % sudo gem install vcs-0.5.2.3.gem
Attempting local installation of 'vcs-0.5.2.3.gem'
ERROR: Error installing gem vcs-0.5.2.3.gem[.gem]: undefined method `include?' for nil:NilClass
:(
>>> "Nicolas" == Nicolas Pouillard <nicolas.pouillard(a)gmail.com> writes:
> You can make a shorter one since title is different form subject.
> Title: "Short"
> Subject: "[Project]: <%= title %> plus something else"
> Thus it's no more possible to make a changelog entry without a tiltle
> and we did it on purpose ;) (we: Akim and I)
Err... I would still promote the use of a title (this is a good
thing), but I would not make it mandatory. In particular, it can
prevent the use of VCS in contexts where this is not the recommended
use.
So I second Roland here.
Hi,
The upcoming Vcs 0.5 (from http://www.lrde.epita.fr/~pouill_n/vcs/)
seems to send malformed e-mails. I've come to this conclusion after
having noticed that
1. there were duplicate headers in e-mails (`From' and `To'). If you
have subscribed to olena-patches, you can see these cloned fields
(unfortunately they aren't visible in Mailman's archives) ;
2. none of the patches I've committed with Vcs 0.5 were visible in the
lrde.olena.patches group, although they have reached the
olena-patches mailing list. This is perhaps because of the sync
mechanism between the mailing list and the newsgroup, which
prevented this maybe-malformed e-mail from going into the group.
I'll temporarily switch back to Vcs 0.4.
The `--non-recursive' option (short option: `-N') doesn't work on
`vcs-svn commit'.
For instance, lets say my working copy contains a new directory and
three new files within this directory:
A tests
A tests/is_a.cc
A tests/properties.cc
A tests/if.cc
A tests/typedef.cc
I just want to commit `tests/if.cc' and `tests/typedef.cc'. With
plain svn, I must mention `tests' in the list of
files-to-be-committed; but to avoid the checkin of `tests/is_a.cc' and
`tests/properties.cc' (due to the default recursive behavior of `svn
commit'), I have to add `--non-recursive' to the command line as well.
This doesn't work with Vcs' front-end to svn (vcs-svn): the
`--non-recursive' option is thrown away and svn adds `tests' and its
files recursively.
I also tried to omit `test' in the vcs-svn command line, but the
result is the same as with vanilla svn: that's forbidden.
[...]
svn: Commit failed (details follow):
svn: '/home/levill_r/src/oln-1.0/metalic/tests' is not under version control and is not part of the commit, yet its child '/home/levill_r/src/oln-1.0/metalic/tests/typedef.cc' is part of the commit
(An obvious workaround is to move away new/modified files from
the working copy at checkin time, but that's quite a regression from
plain svn!).
/tmp % vcs-svn --version
help (?, h): Describe the usage of this program or its subcommands.
usage: help [SUBCOMMAND...]
Valid options:
--version : print client version info
-q [--quiet] : print as little as possible
--config-dir arg : read user configuration files from directory ARG
Hi,
Vcs 0.4 used to have a nice ChangeLog template. While Vcs 0.5's one
is simpler and suffices in most cases, its lack a thing I was using in
Vcs 0.4: choosing the title of a ChangeLog entry (or giving it no
title).
Vcs 0.5 automatically uses the subject from the e-mail form to
generate the title of the ChangeLog entry. In Vcs 0.4, the template
for the ChangeLog entry was less laconic and the title was visible as
a tag:
<%= title %>
I could remove this title, give a longer or shorter title/explanation,
etc.
Would it possible to get this feature back in the forthcoming Vcs?
Thanks in advance!
>>>>> "Nicolas" == Nicolas Pouillard <nicolas.pouillard(a)gmail.com> writes:
Nicolas> On 2/13/06, Roland Levillain <roland(a)lrde.epita.fr> wrote:
>> I can't access this URL (« Forbidden - You don't have permission
>> to access /~pouill_n/vcs/ on this server. »).
Nicolas> J'ai rajouté une page d'index.
Merci !
(En fait, j'avais essayé d'accéder à ton www par le système de
fichiers ; or ce dernier ne contenait pas de répertoire vcs. Je ne me
suis aperçu qu'après que ton répertoire ~/www sur ton compte beyrouth
n'était *pas* un symlink vers ton répertoire ~/www sur ton compte
kualalumpur...)
>>>>> "Nicolas" == Nicolas Pouillard <nicolas.pouillard(a)gmail.com> writes:
Nicolas> I've just made few tests with the beta one (on
Nicolas> www.lrde.epita.fr/~pouill_n/vcs but I can't access it right
Nicolas> now) and it works just fine: the character % can be placed
Nicolas> freely.
I can't access this URL (« Forbidden - You don't have permission to
access /~pouill_n/vcs/ on this server. »).