Fossil import now has a bug that it makes a repo with SHA3 hashes, but
can't do incremental updates because of the SHA3 hashes. My workaround
is to first `fossil new --sha1` and then import. The initial empty
checkin is annoying for importing.
2017-08-17 18:32, Stephan Beal:
> Fwiw: My
Fwiw: My recollection and opinion are the same.
- stephan
Sent from a mobile device, possibly from bed. Please excuse brevity, typos,
and top-posting.
On Aug 17, 2017 07:35, "Andy Bradford" wrote:
> Thus said Andy Goth on Wed, 16 Aug 2017 10:47:56 -0500:
>
> >
Thus said Andy Goth on Wed, 16 Aug 2017 10:47:56 -0500:
> What of this old thread? Are the issues it discusses still pertinent,
> or have they been resolved?
I believe all the relevant issues were actually resolved, however, I
think it was still unfavorable given the time that was
On 07/17/17 03:50, Jan Nijtmans wrote:
The patch below modifies Fossil not to create the initial empty
commit. (I always build Fossil with this patch). Everything works
fine without initial empty commit, the reason this was in Fossil is
just historical. Nowadays, there - indeed - is no reason
2017-07-17 6:33 GMT+02:00 Damien Sykes-Lindley:
> Hi there,
> Is there a way of removing or preventing the creation of the “initial empty
> checkin”? I personally can’t see any practical uses for that, unless the
> implementation somehow requires it.
> Also, this checkin seems to be automatically
On Mon, Jul 17, 2017 at 6:33 AM, Damien Sykes-Lindley <
dam...@dcpendleton.plus.com> wrote:
> Hi there,
> Is there a way of removing or preventing the creation of the “initial
> empty checkin”? I personally can’t see any practical uses for that, unless
> the implementation somehow requires it.
>
Hi there,
Is there a way of removing or preventing the creation of the “initial empty
checkin”? I personally can’t see any practical uses for that, unless the
implementation somehow requires it.
Also, this checkin seems to be automatically sent to trunk. Is there any way of
renaming this
7 matches
Mail list logo