Re: [Tinycc-devel] [BUNDLE] Eliminate many bogus warnings produced during compilation of tcc by gcc

[Joshua Phillips]

The way mercurial works, is that you can pull the changeset to your local 
repository, and no merges or updates are attempted. You can later update to 
that changeset and review it. Also, you can make a "scratch" copy of the 
repository to pull changes into, in case you want to completely discard 
changes.

On Thursday 29 November 2007 18:25:34 Detlef Riekenberg wrote:
> On Do, 2007-11-29 at 09:19 +0000, Joshua Phillips wrote:
> > Once they go into http://hg.sharesource.org/mercurialtcc/, you can get
> > it from there.
>
> I downloaded the mercurialtcc 2 days ago, but the above commit was not
> visible in the web-interface and "hg log" is broken on Ubuntu Dapper:
>   ...
>   File "/usr/lib/python2.4/site-packages/mercurial/commands.py", line
> 326, in show_changeset
>     t, tz = changes[2].split(' ')
>
>
> It works now with the latest stable hg.
> The new hg version has also much more features.
>
> > Otherwise, I'll have to post two copies of every change
>
> I want to see the patch before apply to avoid conflicts with my
> local changes.