Recently I have discovered some very nice features of hg that make it
attractive:
1) Multiple branches such that debian/ can be kept on alioth and have
working copy that has everything if maintainer prefers so
2) MercurialQueues plugin allows to keep versioned quilt patches,
rebase, merge and
On Tue, Sep 1, 2009 at 4:16 PM, Dmitrijs
Ledkovsdmitrij.led...@gmail.com wrote:
Recently I have discovered some very nice features of hg that make it
attractive:
Mercurial Queues are awesome, but there is one major drawback in
Mercurial comparing to SVN - it is impossible to clone a subtree of
On Tuesday 01,September,2009 09:16 PM, Dmitrijs Ledkovs wrote:
Recently I have discovered some very nice features of hg that make it
attractive:
1) Multiple branches such that debian/ can be kept on alioth and have
working copy that has everything if maintainer prefers so
2) MercurialQueues
On Tue, 2009-01-09 at 19:10 +0300, anatoly techtonik wrote:
On Tue, Sep 1, 2009 at 4:16 PM, Dmitrijs
Ledkovsdmitrij.led...@gmail.com wrote:
Recently I have discovered some very nice features of hg that make it
attractive:
Mercurial Queues are awesome, but there is one major drawback in
Hi,
On Wed, Sep 02, 2009 at 12:15:44AM +0800, Chow Loong Jin wrote:
Git has #1, by the way, if I'm understanding you correctly. Which means both
...
In my case, the more I read about Mercurial, the more I dislike it, but
that's a
different matter.
I'm not sure anyone cares, but at Logilab
Hi
Dne Sat, 29 Aug 2009 03:58:13 +0300
anatoly techtonik techto...@gmail.com napsal(a):
If we are all Python developers to some degree and know about PEP 374
- what do you think about switching from SVN to HG for maintaining
Debian packages? There is also convert extension that may allow to
I'm all for Git.
--
Kind regards,
Chow Loong Jin (GPG: 0x8F02A411)
Ubuntu Contributing Developer
signature.asc
Description: OpenPGP digital signature
anatoly techtonik wrote:
If we are all Python developers to some degree and know about PEP 374
- what do you think about switching from SVN to HG for maintaining
Debian packages? There is also convert extension that may allow to
convert history from other sources to HG and PEP 385 that may
OoO En cette nuit striée d'éclairs du samedi 29 août 2009, vers 02:58,
anatoly techtonik techto...@gmail.com disait :
If we are all Python developers to some degree and know about PEP 374
Decision presented in PEP 374 does not really apply to us:
- Windows support is unimportant
- Python
On 2009-08-26 10:59, Alexander GQ Gerasiov wrote:
project on alioth looks nearly dead. We're using trac actively in our
lab, so I'll think about entering team to help them a little bit.
I wonder, how people feel about moving Trac from its own team
to a larger, more active team, i.e. Debian
[Jan Dittberner, 2009-08-28]
On 2009-08-26 10:59, Alexander GQ Gerasiov wrote:
I wonder, how people feel about moving Trac from its own team
to a larger, more active team, i.e. Debian Python Modules Team,
[...]
I would really like to have trac in DPMT
or maybe PAPT (is trac module used
On Fri, Aug 28, 2009 at 10:48:48AM +0200, W. Martin Borgert wrote:
On 2009-08-26 10:59, Alexander GQ Gerasiov wrote:
project on alioth looks nearly dead. We're using trac actively in our
lab, so I'll think about entering team to help them a little bit.
I wonder, how people feel about
[W. Martin Borgert, 2009-08-28]
On 2009-08-28 11:29, Piotr Ożarowski wrote:
or maybe PAPT (is trac module used outside trac itsefl? If not, it
should be moved to private directory, IMHO)
I think, it's in the similar category as Django etc. i.e. it is
a base technology on that you install
On 2009-08-28 12:08, Piotr Ożarowski wrote:
question is: are these plugins installed in trac's directory or do they
import trac?
AFAIK, this depends on the package. Typical plugins are
installed into Trac directories, but they have also to import
trac to use the APIs.
I'm currently not near my
Fri, 28 Aug 2009 11:01:37 +0200
Jan Dittberner ja...@debian.org wrote:
On Fri, Aug 28, 2009 at 10:48:48AM +0200, W. Martin Borgert wrote:
On 2009-08-26 10:59, Alexander GQ Gerasiov wrote:
project on alioth looks nearly dead. We're using trac actively in
our lab, so I'll think about
Twas brillig at 12:21:21 28.08.2009 UTC+02 when deba...@debian.org did gyre and
gimble:
WMB Typical plugins are installed into Trac directories,
?
There are two modes of installation: putting the .egg to the concrete
Trac instance and installing it site-wide in the PYTHONPATH. You're
On 2009-08-28 17:25, Mikhail Gusarov wrote:
There are two modes of installation: putting the .egg to the concrete
Trac instance and installing it site-wide in the PYTHONPATH. You're
probably referring to former.
Distribution-friendly way is latter.
Than I was wrong. I thought that plugins
W. Martin Borgert schrieb:
On 2009-08-26 10:59, Alexander GQ Gerasiov wrote:
project on alioth looks nearly dead. We're using trac actively in our
lab, so I'll think about entering team to help them a little bit.
I wonder, how people feel about moving Trac from its own team
to a larger,
Christoph Egger wrote:
I have some of the trac-plugins ITA/ITPed and would probably consider
following trac itself into one of the python Teams. However I wonder how
the $VCS will be handled, throwing away trac's git history doesn't sound
like a good idea to me.
As my packages
Quoting Christoph Egger deb...@christoph-egger.org:
I have some of the trac-plugins ITA/ITPed and would probably consider
following trac itself into one of the python Teams. However I wonder how
the $VCS will be handled, throwing away trac's git history doesn't sound
like a good idea to
Bernd Zeimetz be...@bzed.de (28/08/2009):
long time, actually there is even a plan (at least in my head) to
make it possible to have modules in git or svn while still being
able to checkout all of them in a useful way, but that means writing
new code, and I didn't have the time to do so yet.
Cyril Brulebois wrote:
Bernd Zeimetz be...@bzed.de (28/08/2009):
long time, actually there is even a plan (at least in my head) to
make it possible to have modules in git or svn while still being
able to checkout all of them in a useful way, but that means writing
new code, and I didn't have
On 2009-08-28 12:21, Piotr Ożarowski wrote:
DPMT is fine then
(most important ;-) problem solved)
Maybe not yet: To me it would make sense to maintain Trac and
some Trac plugins in the same team and in the same VCS. DPMT
would be OK for Trac, but probably not for all the plugins,
that are
On Fri, Aug 28, 2009 at 11:48 AM, W. Martin Borgertdeba...@debian.org wrote:
I wonder, how people feel about moving Trac from its own team
to a larger, more active team, i.e. Debian Python Modules Team,
which already has some of tracs dependencies, i.e.
libapache2-mod-python, mod-wsgi,
24 matches
Mail list logo
