Log message: From: To:
Path:
Author:
Issue:
File name:
File type:
Activity by path
Activity by time
2008-04
Activity by year and month
Activity by author
authors by first/last commit
Core group
Developer turnover
Changes    Collaboration    Timeline    Rss   
1 - 20 of 5847  Next ›
5847 09.01.2008 14:41:30, by shunichi.goto@gmail.com:
New extension to support problematic MBCS on Windows.
The aim of this extension is to clear the problem related to having
0x5c in 2nd byte of encoded bytes. So this extension is usefull for:
* Japanese Windows user shift_jis encoding.
* Chinese Windows user using big5 encoding.
To use this extension, simply enable it without any customization.
Note that some important python built-in functions and mercurial
functions are altered for this extension to convert argument if need
to handle MBCS.
5846 09.01.2008 13:30:37, by shunichi.goto@gmail.com:
Fix not to use os.sep directly.
This change is intended for MBCS support.
5845 09.01.2008 13:30:36, by shunichi.goto@gmail.com:
Add util.splitpath() and use it instead of using os.sep directly.
This change is intended to allow hooking splitpath() by win32mbcs
extension for MBCS support.
5844 09.01.2008 13:30:35, by shunichi.goto@gmail.com:
Add endswithsep() and use it instead of using os.sep and os.altsep directly.
This change is intended to allow hooking endswithsep() by win32mbcs
extension for MBCS support.
5843 09.01.2008 13:30:13, by shunichi.goto@gmail.com:
Use util.normpath() instead of direct path string operation.
This change is intended to allow hooking normpath() by win32mbcs
extension for MBCS support.
5842 11.01.2008 21:06:05, by shunichi.goto@gmail.com:
svn: fix copy exception
5841 11.01.2008 21:06:05, by mpm@selenic.com:
posixfile_nt: set closed early
Exceptions in __init__ may leave us with close undefined in __del__
5840 09.01.2008 17:00:18, by willmaier@ml1.net:
Don't use the -i option with sed
This patch fixes test-keyword on platforms without GNU sed (like
OpenBSD).
5839 09.01.2008 00:27:33, by ed.gomez@free.fr:
convert: respect hg.tagsbranch setting
5838 05.01.2008 21:35:46, by jesse.glick@sun.com:
Issue #880: Simple misspelling ('occured') in web error message.
5837 11.01.2008 02:36:20, by mark.williamson@cl.cam.ac.uk:
Tweak finddate to pass date directly.
Previous implementation was passing (date + "to" + date), which fails
when "<" and friends are prepended to the date specifier.
Signed-off-by: Mark Williamson <mark.williamson@cl.cam.ac.uk>
5836 09.01.2008 11:15:00, by michele.cella@gmail.com:
adding "prefix" option to "hg serve" (command line and [web] section)
allows "hg serve" to serve from a different path than '/' (server root)
5835 09.01.2008 04:12:30, by kevin.christen@gmail.com:
Fix XHTML validation error on file diff page.
Replaces <div>, a block level element, with <span>, it's inline
counterpart, in <pre>, which is also an inline element.
5834 11.01.2008 20:06:38, by mpm@selenic.com:
hook: redirect stdout to stderr for ssh and http servers
5833 11.01.2008 04:07:43, by mdounin@mdounin.ru:
convert: add commandline.xargs(), use it in svn_sink class
Introduce commandline.xargs() to limit argument list with respect
to ARG_MAX bytes. If no ARG_MAX information available - use POSIX
required minimum of 4096 bytes.
Under Windows, while actual argument list length is limited to 32k,
shells impose their own limits on command line length, down to 2047 bytes
for cmd.exe under Windows NT/2k and about 2500 bytes for older 4nt.exe.
See http://support.microsoft.com/kb/830473 for details about cmd.exe
limitations.
Since ARG_MAX is limit for argument list and environment, we reserve half
of it and one byte for environment variables. This way with default ARG_MAX
(4096 bytes) we get value 2047 bytes which is OK for Windows too.
5832 11.01.2008 15:01:29, by blacktrash@gmx.net:
keyword: fix some doc strings; update copyright
5831 10.01.2008 10:07:18, by kirr@mns.spb.ru:
hg qrecord -- like record, but for mq
I'm a former Darcs user, and I've discovered that it is very convenient to
actually perform development using MQ first, and only when the patches are
'ready' move them to project's history in stone.
Usually I work on some topic, temporarily forgetting about any version control,
and just do coding, experimenting, debugging, etc.
After some time, I approach a moment, where my work should actually go to
patches/commits, and here is the problem::
As it is now, there is no way to put part of the changes into one patch,
and another part of the changes into second patch.
This works, but only when changes are touching separate files, and for
semantically different changes touching the same file(s) there is now
pretty way to put them into separate patches.
For some time, I've tolerated the pain to run vim patches/... and move hunks
between files by hand, but I think this affects my productivity badly.
So, here is the first step towards untiing the problem:
Let's use 'hg qrecord' for mq, like we use 'hg record' for usual commits!
5830 10.01.2008 10:07:18, by kirr@mns.spb.ru:
cmdutil.commit: extract 'addremove' from opts carefully
we are going to use cmdutil.commit for qrecord, and it's brother
qrefresh does not support addremove.
5829 10.01.2008 10:07:18, by kirr@mns.spb.ru:
dispatch: allow extensions to provide setup code
we'll need this soon, when record extension will optionally depend
on mq early -- when preparing cmdtable.
Also, if accepted, ExtensionHowto wiki should be updated as well.
5828 10.01.2008 10:07:13, by kirr@mns.spb.ru:
record: refactor record into generic record driver
rationale
---------
I'd like to make MQ version of record -- qrecord.
>From the first glance it seemed to be easy -- the task in essence would be to
change call to cmdutil.commit() to something like mq.qrefresh().
As it turned out queue.refresh() and cmdutil.commit() have different semantics
-- cmdutil.commit() first scans for changes and then delegate the actual commit
to lowlevel func. On the other hand queue.refresh() do it all in once, and I am
a bit scary to change it.
Maybe the right way would be to first refactor queue.refresh() to use
cmdutil.commit() machinery, and then trivially adjust record, but I feel I'm
not competent for the task right now.
Instead, I propose we refactor record to be some sort of high-level driver, or
like a high-level decorator one can say, which will first interactively filter
changes, and then delegate commit job to high-level commiter, e.g. 'commit' or
'qrefresh'
So, this patch does just that -- refactor record to be generic driver, and
update 'hg record' code to use the driver.
'hg qrecord' will follow.
1 2 3 4 5 6 7 8 9 10 Next