On Wed, Jan 6, 2016 at 8:46 PM, Joe Mistachkin
wrote:
> Thanks for the report. Should be fixed, here:
>
> https://www.fossil-scm.org/index.html/vinfo/18607?sbs=0
Completely unrelated: i thought the UID output had been changed to output
at least enough of a UID to include at least 1 alp
Florian Balmer wrote:
>
> 7-Zip lists "D" as the attributes for empty files in the
> fossil-generated zips, and `zipinfo' on my FreeBSD web server lists
> "drwxr-xr-x".
>
Thanks for the report. Should be fixed, here:
https://www.fossil-scm.org/index.html/vinfo/18607?sbs=0
Please
On Wed, Jan 6, 2016 at 4:18 AM, Stephan Beal wrote:
>
> i agree with Andy B. that "publish" is not the right command here - that's
> intended for bundles, as i understand it. i've no experience with bundles.
>
The docs suggest it's also applicable to ant private artifacts and branches:
"Cause ar
On Wed, Jan 6, 2016 at 10:18 AM, Stephan Beal wrote:
> From what i remember in libfossil, it is possible to go from private to
> public, but never the reverse. Mixing private content with public in a
> commit causes, if i'm understanding the code correctly, the whole commit to
> be made private.
On Tue, Jan 5, 2016 at 8:32 PM, bch wrote:
> On 1/5/16, Richard Hipp wrote:
> > On 1/5/16, Richard Hipp wrote:
> > Even after rebuilding, the check-in shows up as "unpublished".
> > There's a bug somewhere in the "private" tag handling. Who can be the
> > first to find it!
>
> I think we've go
I'm using a custom set of scripts to transfer commits from one
repository to another. The scripts parse the output of `fossil whatis'
to grab the check-in comments and time stamps, extract the files with
`fossil zip', and re-commit everything to the target repository.
Recently, after updating the
6 matches
Mail list logo