Projects

projects@lrde.epita.fr

1049 discussions

Re: [Projects] Vcs 0.5: Request for feature: more flexible ChangeLog entry

by Akim Demaille

>>> "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.

19 years, 4 months

vcs-svn up 0.5: fails

by Akim Demaille

~/lectures/lrde-admin-lrde % svn up nostromo 15:08 svn: Can't convert string from native encoding to 'UTF-8': svn: architecture-r?\233seau.tex vcs: error: command: svn update -- vcs: error: exit: 1 ~/lectures/lrde-admin-lrde % \svn up nostromo Err 1 At revision 81.

19 years, 4 months

Vcs 0.5: Malformed e-mails?

by Roland Levillain

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.

19 years, 4 months

Vcs: lack of support for --non-recursive

by Roland Levillain

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!).

19 years, 4 months

vcs-svn ci --help

by Akim Demaille

~/src/tc % svn ci --help nostromo Err 1 vcs: info: Updating your working copy... Authentication realm: <https://svn.lrde.epita.fr:443> LRDE Public Subversion repository Password for 'akim': Authentication realm: <https://svn.lrde.epita.fr:443> LRDE Public Subversion repository Username: Password for '': Authentication realm: <https://svn.lrde.epita.fr:443> LRDE Public Subversion repository Username: Password for '': svn: PROPFIND request failed on '/svn/tc/trunk/tc' svn: PROPFIND of '/svn/tc/trunk/tc': authorization failed (https://svn.lrde.epita.fr) vcs: error: command: svn update -- vcs: error: exit: 1

19 years, 4 months

svn --version broken

by Akim Demaille

/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

19 years, 4 months

Vcs 0.5: Request for feature: more flexible ChangeLog entry

by Roland Levillain

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!

19 years, 4 months

Re: [Projects] Vcs: literal `%' in ,form file

by Roland Levillain

>>>>> "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...)

19 years, 4 months

Re: [Projects] Vcs: literal `%' in ,form file

by Roland Levillain

>>>>> "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. »).

19 years, 4 months

Re: [Projects] Re: Test suite

by Roland Levillain

>>>>> "Nicolas" == Nicolas Pouillard <nicolas.pouillard(a)gmail.com> writes: Nicolas> On 1/26/06, Roland Levillain <roland(a)lrde.epita.fr> wrote: >> >>>>> "Nicolas" == Nicolas Pouillard <nicolas.pouillard(a)gmail.com> >> writes: Nicolas> Soit dit en passant il faut toujours que l'on fasse cette Nicolas> presentation d'Uttk ce qui permettra de mettre les choses au Nicolas> claire dans la tête de tout le monde. >> Je suis preneur ! (Je ne pense pas être le seul). Est-ce que vous >> avez du temps pour ça ? Nicolas> Pas tout de suite mais dans un mois par exemple, genre un Nicolas> mercredi disons le 22 fevrier si cela vous arrange. Mais cela Nicolas> dépend peut être de vos contraintes si le choix des Nicolas> technologies doit être absolument fait plus tôt ou pas ? Le 22/2 me semble une bonne date. Mises à part les réunions usuelles, le calendrier indique qu'il y a une réunion Transformers de 14h à 16h. Est-ce que tu auras/vous aurez un créneau compatible avec cet emploi du temps ? Au passage, si vous pouviez présenter (même rapidement) Vcs aux nouveaux, ce serait super !

19 years, 4 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Projects