Am Mittwoch 11 Juni 2008 03:56:06 schrieb [EMAIL PROTECTED]:
> > That means, that the Mercurial people say, that history should be
> > preserved in most cases, so it wasn't first priority.
>
> This is precisely the sort of policy decisions that the software should
> not impose upon users.
Git deci
Hi,
On Sun, Jun 08, 2008 at 01:39:51AM +0200, Arne Babenhauserheide wrote:
> Am Samstag 07 Juni 2008 18:19:29 schrieb [EMAIL PROTECTED]:
> > Err... Does that mean that Mercurial doesn't even offer rebase (and
> > it can't be implemented trivially)?!
>
> That means, that the Mercurial people say,
Am Samstag 07 Juni 2008 18:19:29 schrieb [EMAIL PROTECTED]:
> Err... Does that mean that Mercurial doesn't even offer rebase (and it
> can't be implemented trivially)?!
That means, that the Mercurial people say, that history should be preserved in
most cases, so it wasn't first priority.
It can
Hi,
On Wed, Jun 04, 2008 at 10:38:53AM +0200, Arne Babenhauserheide wrote:
> I'm interested in how they are going to tackle that in the Summer of
> Code project.
>
> I didn't find information about the way they want to do it in the
> short description (and I don't have the time to investigate r
Sorry, forgot to forward to the list...
But while I'm at it: To me "pathological" doesn't mean bad, but simply "a very
seldomly appearing case", as out maths profs use it - I just realized that
the expression could be easily taken wrong.
And: Many thanks for the info about changes in Linux! T
Am Mittwoch 04 Juni 2008 07:33:10 schrieb Ivan Shmakov:
> > Mercurial offers the same, for GNU/Linux and Windows.
>
> Indeed.
>
> I assume that it will break the hard link as soon as a change is
> committed for the file?
Yes (I just tested it).
Result: As soon as you commit a
