You cannot edit history that has already been shared with other clones.
If you did, it would just come back at the next pull.
--
Sjoerd Mullender
signature.asc
Description: OpenPGP digital signature
___
Python-Dev mailing list
Python-Dev@pyth
ot actually sure this can be done, and if it can, how), or
you can merge the two changesets: hg update -C 68309; hg merge 68802; hg
commit. And finally, you can rebase: hg rebase -s 68309 -d 68802. The
rebase will graft your changeset on top of Martin's.
>
> S
--
Sjoerd Mullende
ed changesets will be fetched again from the source clone
(they had been removed from yours, so aren't there anymore) and you will
get a similar graph again, but now the S1 will be a list of changesets
instead of the one.
--
Sjoerd Mullender
signature.asc
Description: OpenPGP dig
fter which you can use hg
glog to look at your clone. Look in particular at the changeset which
is marked with an @ sign instead of an o. That (or those if you're in
the middle of a merge) is the "parent" of your working set.
--
Sjoerd Mullender
signature.asc
Description: OpenP
\
> \ --> ... Cn
>
> (where S1 is my local change and C? are the central changesets)
>
> Rebase will do this, right?
>
> C1 --> C2 --> ... --> Cn --> S1
>
> Am I going to have to rebase then every time I re-pull that repositor
-u, you could have used hg pull --rebase (after
enabling the extension) to do the rebase automatically. But that is for
next time.
--
Sjoerd Mullender
signature.asc
Description: OpenPGP digital signature
___
Python-Dev mailing list
Python-Dev@py
On 2010-02-19 16:23, Nick Coghlan wrote:
> Sjoerd Mullender wrote:
>> My point is, as a matter of *policy*, nothing should be released that
>> uses deprecated stuff. I can't create a bug report about wrong (or
>> incomplete) policies.
>
> The policy is more tha
On 2010-02-19 14:45, Eric Smith wrote:
> Sjoerd Mullender wrote:
>> On 2010-02-19 14:10, Guido van Rossum wrote:
>>> Isn't mhlib itself deprecated? (It's gone in Py3k.)
>>
>> I wouldn't like that, but it is beside my point. If a module is
>> depr
. mhlib uses
multifile and multifile does tell you it is deprecated, and that is
pretty annoying.
> On Fri, Feb 19, 2010 at 4:33 AM, Sjoerd Mullender wrote:
>> I have noticed that deprecated stuff is still being used in the standard
>> Python library. When using modules that
cated
constructs in non-deprecated (or otherwise deprecated) modules.
The case I am running into is that mhlib uses multifile (in 2.6).
--
Sjoerd Mullender
signature.asc
Description: OpenPGP digital signature
___
Python-Dev mailing list
Python-Dev@python.org
On 2008-05-07 13:37, Amaury Forgeot d'Arc wrote:
Hello,
2008/5/7 Sjoerd Mullender <[EMAIL PROTECTED]>:
Why does sock.close() not actually close sock?
If I run the code
import socket
sock = socket.socket()
...
sock.close()
I would expect that a system call is done to actuall
replaces the socket instance with a dummy
instance so that all subsequent calls on the sock object fail, but it
does nothing else!
--
Sjoerd Mullender
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
ch direction this works (is East
positive or negative?), and I will need to change this number twice
yearly. In other words, it shouldn't be a number, it should be a name,
like the names used in Linux: Europe/Amsterdam.
Looks nice otherwise.
--
Sjoerd Mullender
_
On 03/16/2007 05:43 PM, Nick Coghlan wrote:
--
Sjoerd Mullender
> Phillip J. Eby wrote:
>> At 01:31 PM 3/16/2007 +0100, Martin v. Löwis wrote:
>>> Phillip J. Eby schrieb:
>>>> 2. Add an optional flag argument to enable the new behavior
>>> How would th
On 03/09/2007 08:56 PM, Martin v. Löwis wrote:
--
Sjoerd Mullender
> Christian Heimes schrieb:
>> BJörn Lindqvist schrieb:
>>> I think it should be a ValueError, given that the programmer is very
>>> likely to further use the returned timestamp to for example insert
&g
tter in most of
these cases), but it's easy to add a "= 0" to the declaration of the
variable to shut up the compiler, hopefully with a comment saying as
much. That's what I've been doing in my code that generated these
warnings. It
s too
often in backward incompatible ways. They even suggested using that
other P language because that was much more backward compatible.
Check out the thread starting at
https://www.redhat.com/archives/fedora-list/2005-August/msg01682.html .
--
Sjoerd Mullender
sign
_
> Python-Dev mailing list
> [EMAIL PROTECTED]
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> http://mail.python.org/mailman/options/python-dev/sjoerd.mullender%40cwi.nl
--
Sjoerd Mullender
signature.asc
De
th different
> versions of GCC. Is this behavior intentional?
Configure with --without-cxx to not use g++. Since there is an option
in configure, I assume it is intentional.
--
Sjoerd Mullender
___
Python-Dev mailing list
Python-Dev@python.org
http://
l receive
every message sent to the mailing list."
In other words, don't check any topics, and you get everything. If you
*do* check a topic, you only get the messages belonging to that topic.
This seems to me a reasonable default.
--
Sjoerd Mullender <[EMAIL PROTE
n if it is
defined else it defaults to the value the shell has.
It's autoconf that deals with these flags. See the output of "configure
--help".
--
Sjoerd Mullender <[EMAIL PROTECTED]>
signature.asc
Description: OpenPGP digital signature
21 matches
Mail list logo
