2015-03-20 4:56 GMT+01:00 Richard Hipp d...@sqlite.org:
I rue the day that I allowed that patch to land on trunk.
But it is all fixed now - you won't have the problem with 1.32.
Note that the initial empty commit is an unique feature of
fossil, GIT and SVN don't have that. Abilio started with
a
On Fri, 20 Mar 2015 11:46:14 +0200
John Found johnfo...@asm32.info wrote:
On Thu, 19 Mar 2015 22:36:56 -0430
Abilio Marques abili...@gmail.com wrote:
I started to think: what does it mean to have multiple independent
check-outs? And I knew I wouldn't be able to sleep well because of not
On Thu, 19 Mar 2015 22:36:56 -0430
Abilio Marques abili...@gmail.com wrote:
I started to think: what does it mean to have multiple independent
check-outs? And I knew I wouldn't be able to sleep well because of not
knowing. So I created a new test repo, and began:
It really surprised me. Using
David Macek wrote:
First, there's the option of cloning the repository locally, which will result
in two working copies you can work on independently. Maybe too independently,
as each working copy has its own repo. If you want to see some structure there,
you can keep one clone as a bare repo
On 20. 3. 2015 21:30, Warren Young wrote:
On Mar 19, 2015, at 9:27 PM, Richard Hipp d...@sqlite.org wrote:
There is no documentation because I could not conceive of wanting to
use a VCS in any other way.
It’s been several years since Git emerged as top dog in the DVCS race, so
there must
On Mar 19, 2015, at 9:27 PM, Richard Hipp d...@sqlite.org wrote:
There is no documentation because I could not conceive of wanting to
use a VCS in any other way.
It’s been several years since Git emerged as top dog in the DVCS race, so there
must be a significant number of people who have
After reading Mr. Hipp answer to some previous email about git saying:
So the staging area is being used as a way of working around the fact
that Git does not allow multiple independent check-outs against the
same repository? Am I understanding that correctly?
I started to think: what does it
On 3/19/15, Abilio Marques abili...@gmail.com wrote:
After reading Mr. Hipp answer to some previous email about git saying:
So the staging area is being used as a way of working around the fact
that Git does not allow multiple independent check-outs against the
same repository? Am I
On 3/19/15, Abilio Marques abili...@gmail.com wrote:
PS: after running my quick test in fossil 1.31, I ended with two separate
artifacts, both on trunk, but without a common ancestor. I'm running
Ubuntu, and I haven't compiled the 1.32. I believe that version was
released as a patch for this
I imagined some of those scenarios right away after my experiment... Some
are great... Until today, I was doing a fossil clone file:// or ssh:// ...
Now I can deal with just a single copy of the repo.
I only see it quickly and indirectly mentioned in section 2.3 here:
10 matches
Mail list logo
