Barry Warsaw writes:
> You mean, TortoiseHg supports incremental commits on a single file? That's
> kind of neat, but scary. ;)
Darcs people have been doing this for, well, for as long as Darcs has
existed. It's not scary at all. In fact, in Darcs you can select
hunks across files, too.
__
On 2011-02-27 23:21, Neil Hodgson wrote:
> Adrian Buehlmann:
>
>> FWIW, we are very close to releasing TortoiseHg 2.0 (due March 1st),
>> which ported the current Gtk based TortoiseHg to Qt (although, it was
>> more like a rewrite :-).
>
>I hope this is going to be fast.
Here, the Workbench
Adrian Buehlmann:
> FWIW, we are very close to releasing TortoiseHg 2.0 (due March 1st),
> which ported the current Gtk based TortoiseHg to Qt (although, it was
> more like a rewrite :-).
I hope this is going to be fast. One of the reasons I chose Hg over
Bzr for another project was that the B
Scott Dial:
> I don't believe TortoiseHG has such a feature (or I can't find it),
> although if you have TortoiseSVN, you can still use that as a patch tool.
The Import... command is in the Synchronize menu of Hg Repository Explorer.
There is no GUI equivalent to --no-commit but you can ex
Guido van Rossum wrote:
Ok. Will you hvae time to port your patches to 3.3?
I'm not sure -- I'll see what I can do.
--
Greg
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail
>> My assumption was that most developers don't use MSVC, so most of them
>> don't risk breaking eols ;)
>> True, for Windows devs it might be necessary to promote it.
>
> Windows devs were the original target audience, yes :)
I meant to say that earlier: thanks to everybody involved in the
origi
>> I think this is overly optimistic. Visual Studio will break all your
>> files if you don't use that extension (and you actually use it to
>> modify source code).
>
> My assumption was that most developers don't use MSVC, so most of them
> don't risk breaking eols ;)
> True, for Windows devs it
On 26.02.2011 21:49, Barry Warsaw wrote:
> On Feb 26, 2011, at 01:49 AM, Éric Araujo wrote:
>
>>You speak to my heart, sir. In your ~/.hgrc, under the section [ui],
>>set “editor = path/to/mercurial/source/hgeditor” and enjoy your diffs.
>>I use it and love it.
>
> Except it doesn't quite work t
Le 27/02/2011 16:22, Antoine Pitrou a écrit :
>> - Remove one XXX that was in a warning block, not a comment
> Well, this is a XXX because that means we could find something else to
> advocate, not because the reader must take it as a warning.
My point was that that should be either a comment with
Le 27/02/2011 16:21, Antoine Pitrou a écrit :
>> summary:
>> patchcheck does work
> How does it find out which changesets it should operate on?
It operates on changed files, just like with Subversion:
http://hg.python.org/cpython/file/tip/Tools/scripts/patchcheck.py#l40
→ hg status --added --mod
On 2011-02-27 16:35, Scott Dial wrote:
> On 2/27/2011 10:18 AM, Antoine Pitrou wrote:
>> Well, chances are TortoiseHG comes with an UI to apply patches
>> (TortoiseSVN had one), so the command-line instructions may be of
>> little use to them.
>
> I don't believe TortoiseHG has such a feature (or
On 2/27/2011 10:18 AM, Antoine Pitrou wrote:
> Well, chances are TortoiseHG comes with an UI to apply patches
> (TortoiseSVN had one), so the command-line instructions may be of
> little use to them.
I don't believe TortoiseHG has such a feature (or I can't find it),
although if you have TortoiseS
On Sun, 27 Feb 2011 04:17:09 +0100
eric.araujo wrote:
>
> - Move a link target after its use
> - Add a todo about tracker markup
> - Remove one XXX that was in a warning block, not a comment
Well, this is a XXX because that means we could find something else to
advocate, not because the reader m
On Sat, Feb 26, 2011 at 11:48 PM, Nick Coghlan wrote:
> On Sun, Feb 27, 2011 at 5:26 PM, "Martin v. Löwis"
> wrote:
> > If you think that it's a likely problem that people create named
> > branches by mistake, then we should have a hook.
>
> I suspect the concern is that people may create named
On Sun, 27 Feb 2011 04:17:07 +0100
eric.araujo wrote:
> summary:
> patchcheck does work
How does it find out which changesets it should operate on?
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
On Mon, Feb 28, 2011 at 1:12 AM, Antoine Pitrou wrote:
> On Sun, 27 Feb 2011 07:46:51 +0100
> "Martin v. Löwis" wrote:
>> > Actually, it isn't *required* on each developer's setup, since we
>> > now have a hook that refuses bogus changegroups (if needed, we can even
>> > refuse individual changes
On Sun, Feb 27, 2011 at 2:42 AM, Adrian Buehlmann wrote:
> On 2011-02-26 23:26, Greg Ewing wrote:
> > There are *some* topological restrictions, because hg won't
> > let you assign a branch name that's been used before to a node
> > unless one of its parents has that name. So you can't create
> >
On Sun, 27 Feb 2011 04:17:06 +0100
eric.araujo wrote:
> Advertise hg import over patch.
>
> hg import understands the extended git diff format, which supports renames,
> changes to the executable bit and changes in binary files.
Yes, but it's too easy to forget the awkward "--no-commit" option
On Sun, 27 Feb 2011 07:46:51 +0100
"Martin v. Löwis" wrote:
> > Actually, it isn't *required* on each developer's setup, since we
> > now have a hook that refuses bogus changegroups (if needed, we can even
> > refuse individual changesets). In most situations, even without the
> > eol extension l
On Sun, 27 Feb 2011 08:09:21 +0100
"Martin v. Löwis" wrote:
> >> changeset: 72694:e65daae6cf44
> >> user:Antoine Pitrou
> >> date:Mon Feb 21 21:30:55 2011 +
> >> summary: Try s/UINT_MAX/INT_MAX/
> >
> > It's not on an unnamed branch, it's on the "default" branch (which
On Sun, Feb 27, 2011 at 06:31, brett.cannon wrote:
> +When writing new tests to increase coverage, do take note of the style of
> tests
> +already provided for a module (e.g., whitebox, blackbox, etc.). As
> +some modules are primarily maintained by a single core developer they may
> have
> +a s
On Sun, Feb 27, 2011 at 03:17, eric.araujo wrote:
> eric.araujo pushed f325d743c385 to devguide:
>
> http://hg.python.org/devguide/rev/f325d743c385
> changeset: 331:f325d743c385
> branch: hg_transition
> user: ?ric Araujo
> date: Sat Feb 26 17:30:51 2011 +0100
> summary:
> p
On 2011-02-26 23:26, Greg Ewing wrote:
> From: Antoine Pitrou
>> - a "branch" usually means a "named branch": a set of changesets
>> bearing the same label (e.g. "default"); that label is freely chosen
>> by the committer at any point, and enforces no topological
>> characteristic
>
> There
>> It's not a matter of dependence on iteration order, but of
>> reproducibility (in my case there were minor numerical differences due
>> to different iteration orders).
>
> Can you give a code example? I don’t understand your case.
It's a bit involved (that's why it took me a while to locate t
24 matches
Mail list logo
