gt; well here ... it would take a little thought to design an appropriate
> workflow, anyway.
Yeah, you guys should try it out first -- it's easy to introduce named
branches later if you want.
--
Martin Geisler
Mercurial links: http://mercurial.ch/
pgpRzl80o4Dzb.pgp
Description: PGP
geset. This is similar to how TCP checksums are computed.
This increases the size of each changeset by about 2 KB of data which
cannot be compressed -- this adds up over time and I would only advice
people to use the extension if they are very paranoid or have special
legal requirements.
--
Mar
Georg Brandl writes:
> Am 08.07.2010 17:44, schrieb Martin Geisler:
>> Steve Holden writes:
>>
>>> Martin Geisler wrote:
>>>> "Stephen J. Turnbull" writes:
>>>>
>>>>> Just ask Martin, there are too many possibili
Steve Holden writes:
> Martin Geisler wrote:
>> "Stephen J. Turnbull" writes:
>>
>>> Just ask Martin, there are too many possibilities here to worry
>>> about. If maybe we want it, and he is willing to contribute the
>>> parts he wrote
ote to Python under Python's license, then we can worry about
> whether we really want it and about how much any required hoop-jumping
> will cost.
I would be happy to relicense it under the Python license.
--
Martin Geisler
aragost Trifork: Professional Mercurial support
http://a
y. I'm not a Docutils developer, but to me it seems that Docutils
is now a very stable and widely used package, so it would IMHO make
sense to include it.
--
Martin Geisler
Mercurial links: http://mercurial.ch/
pgpf0R31gMZHO.pgp
Description: PGP signature
__
s that same the branch name, but the graph itself works
the same.
The nice thing about our current setup is that I can do
hg update stable
and the name 'stable' is then interpreted as the tip-most changeset on
the stable branch.
--
Martin Geisler
Mercurial links: http://mer
them. Without bookmarks
you can of course look at 'hg heads' or some other log viewer.
http://mercurial.selenic.com/wiki/BookmarksExtension
Since Mercurial 1.6, you can push and pull the bookmarks between
repositories. They used to be local only, but this is now solved. See
the botto
ates it.
However, you are free to mix the upstream clones into a single clone if
you want (with 'hg pull' from different upstream repositories), or you
can keep them separate.
If the upstream uses a single repository with multiple named brancehs,
then you can still maintain separate clon
Dirkjan Ochtman writes:
Hi everybody!
I hope you have fun at PyCon :-)
> As for the current state of The Dreaded EOL Issue, there is an
> extension which seems to be provide all the needed features, but it
> appears there are some nasty corner cases still to be fixed. Martin
> Geis
hon.devel
I don't know why the search box at the bottom of
http://news.gmane.org/gmane.comp.python.devel
fails...
--
Martin Geisler
VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.
, etc. Outside a handful of
> people on this list, I have yet to see anyone adopt it as the
> preferred syntax.
I've skimmed over the PEP, and the new {}-syntax seems to have some nice
features. But I've not seen it used anywhere yet.
--
Martin Geisler
VIFF (Virtual Ideal
In the configuration file, there is a section [patterns] which
> maps file name patterns to conversion modes, e.g.
>
> [patterns]
> **.txt = native
> **.py = native
> **.dsp = CRLF
> **.bat = CRLF
> Tools/bgen/README = native
> Lib/email/test/data/msg_26.txt = CRLF
>
>
s:
http://mercurial.selenic.com/wiki/MqExtension
http://mercurial.selenic.com/wiki/HisteditExtension
The problem comes if a small group have been working together on a new
feature and have merged changes in from the mainline while doing so.
They will then no longer be able to edit past the most recent m
ok will have to work like this in order for
people to fix mistakes like you just described.
--
Martin Geisler
VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.
pgpJVx1LcPK63.pgp
Description: PGP signatur
ies, rather than
> fixing them automatically.
Okay --- I don't have much experience with the svn:eol-style, except
that I've read about it in the manual.
--
Martin Geisler
VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SM
ehaves like that, as far as I can
tell from a bit of testing).
That way the repository will contain most files in the format specified
as native for it, but selected files are stored using whatever EOLs they
like. The result is that someone who has not enabled the extension will
get correct fil
Paul Moore writes:
> 2009/8/22 Martin Geisler :
>> Oh, we try to be very paranoid in Mercurial :-) That's why you don't
>> see any support for copying hgrc files when you clone and why hg wont
>> trust hgrc files not owned by you: it should be safe to do
>>
&
ntact list. That's what I mean by "social engineering,"
> and why I worry about policy pushback from Mercurial HQ.
>
> Maybe that's more paranoid than they are But it can't hurt your
> cause to be ready for that kind of worry.
Oh, we try to be very para
you can add
%include ../.repo-settings
in your /.hg/hgrc file, and this will result in
/.repo-settings
being loaded (and this file *is* in the working copy and can thus be put
under revision control).
--
Martin Geisler
VIFF (Virtual Ideal Functionality Framework) brings easy and eff
oned!) file named 'config' from the
root of your repository will be included on the spot. The catch is that
you have to add such a line to all your Python clones.
--
Martin Geisler
VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computat
21 matches
Mail list logo
