[EMAIL PROTECTED] (Ludovic Courtès) writes:
> Apparently, `star-merge' saw that MY-BRANCH--patch-9 was merged into
> HIS-BRANCH and made the wrong assumption that _all_ patches prior to
> MY-BRANCH--patch-9 had been merged into HIS-BRANCH.
star-merge computes a common ancestor, and either applies
Hi,
It looks that I encountered a badly-handled corner case for
`star-merge'. But I may as well have simply missed something, so I'd
welcome help.
I'm trying to star-merge my branch with a branch that selectively
replayed _non-contiguous_ patches from my branch:
$ tla merges HIS-BRANCH MY-BRA
[EMAIL PROTECTED] (Ludovic Courtès) writes:
> I think I once read that this (the servers being too loaded) was due to
> tla/baz themselves rather than ArchZoom. Could you give further insight
> in what exactly was causing this high load and whether/how you think
> this could be improved?
I don't
Hi,
Matthieu Moy <[EMAIL PROTECTED]> writes:
> You have also http://gna.org which provided ArchZoom, but recently
> disabled it 'cause their servers were too loaded.
I think I once read that this (the servers being too loaded) was due to
tla/baz themselves rather than ArchZoom. Could you give f
