So, I'm aware of drh's message from 2010-03-06 [1]. Is merging repositories
this way still supposed to work? If so, I'll open a ticket with the
information below. -Martin
[1] http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg01641.html
# background: two teams working on some
Maybe consider moving everything on repo B to a separate branch, so that A
is on trunk, B is on a branch. Then you can issue a merge command on the
home computer, I imagine this would be easier that doing push / merge at the
same time.
Just a thought, but I haven't actually merged two fossil
May be fossil export of one piped on a fossil import of the other one will
work!! I never tried but it might work I don't know how would look like
the timeline when doing that...
--
Martin
Le 2011-08-24 à 16:55, Martin S. Weber martin.we...@nist.gov a écrit :
So, I'm aware of drh's
I really do appreciate all the patches to Fossil that have been coming in
lately. Thanks for the help!!!
But if you look at the timeline (
http://www.fossil-scm.org/fossil/timeline?c=2011-08-24n=40) you'll see that
contributors are putting changes in branches to which they have assigned a
On 08/24/11 18:14, Martin Gagnon wrote:
May be fossil export of one piped on a fossil import of the other one will
work!! I never tried but it might work I don't know how would look like
the timeline when doing that...
Actually I did try fossil deconstruct'ing both repositories into
Hi,
I took the liberty to submit Fossil to Freshmeat. The URL is:
http://freshmeat.net/projects/fossil
Anyone with a Freshmeat account is welcome to rate or write a comment.
While all my published projects are nearly oneliners, I've had a pretty nice
experience with Freshmeat. It seems that a
6 matches
Mail list logo
