This bug was caused simply by trying to write too much data into
a statically-sized character array and not ensuring that the
character array was zero-terminated. As the poster noted,
this wouldn't have caused internal problems, but may have
presented more information to the remote than intended.
I've now created a pdf file to help explain this merge business.
http://projects.codersbase.com/repos/research/Merge.pdf
If you want the source of the document, it's in a darcs repository so
just go up one level with a darcs get:
darcs get http://projects.codersbase.com/repos/research
If you fi
On 7/11/07, Ben Coburn <[EMAIL PROTECTED]> wrote:
Obviously each project has it's own circumstances, so many projects
will use different languages, revision control systems, editors,
etc., etc., etc.. If Mercurial works for you, that's great.
The fact that this problem occurs rather often sugge
Obviously each project has it's own circumstances, so many projects
will use different languages, revision control systems, editors,
etc., etc., etc.. If Mercurial works for you, that's great.
For comparison, I've been contributing to the DokuWiki project
( http://wiki.splitbrain.org/wiki:d
Dear people of darcs-devel:
One my co-workers, Rob, refuses to use darcs for remote operation
anymore. Now he uses rsync to synchronize a local darcs repo with a
remote darcs repo, and uses darcs only locally. This is impacting
our productivity and so it cannot remain, and soon Allmydata.
