Ivan Zakharyaschev wrote:
2015-01-22 13:16 UTC+03:00, Ivan Zakharyaschev i...@altlinux.org:
Actually, after I make the transition to darcs, I'm thinking about a
workflow with a reduced number of branches (no intersection branch
AB), so I won't need a working darcs directory for AB. Does it
Hi,
Fri, 23 Jan 2015 17:16 +0100, Ben Franksen ben.frank...@online.de:
Ivan Zakharyaschev wrote:
2015-01-22 9:53 UTC+03:00, Ganesh Sittampalam gan...@earth.li:
'darcs convert' is currently supported.
So, I believe 'darcs convert --import' doesn't have the notion of Git
branches, does it?
Ivan Zakharyaschev wrote:
Fri, 23 Jan 2015 17:16 +0100, Ben Franksen ben.frank...@online.de:
Ivan Zakharyaschev wrote:
2015-01-22 9:53 UTC+03:00, Ganesh Sittampalam gan...@earth.li:
'darcs convert' is currently supported.
So, I believe 'darcs convert --import' doesn't have the notion of Git
Ben Franksen wrote:
We should really improve the darcs convert import command so that it can
incrementally import using marks files or some other mechanism.
It is a lot simpler than I thought. darcs convert import needs no marksfile
support, that is already done by git fast-export. All that is
Ivan Zakharyaschev wrote:
2015-01-22 9:53 UTC+03:00, Ganesh Sittampalam gan...@earth.li:
'darcs convert' is currently supported.
So, I believe 'darcs convert --import' doesn't have the notion of Git
branches, does it? (At least, there are no examples of using 'darcs
convert --import' on
