>
> i have an Android eMMC module for my odroid, but it won't run on my
> particular monitor (which has only a DVI, not native HDMI, and Android
> doesn't appear to like that via the adapter). It does run on my tv, though.
> At some point i might tinker around with getting sshd and a dev env set up
On Tue, Jul 29, 2014 at 9:22 PM, JR wrote:
> Asking off-list in case this is an embarrassingly stupid question.
>
Replying back to the list because it's a good question and i expected this
question to come along at some point ;)
> What about an Android ARM build (preferably with SSL enabled)?
On Tue, Jul 29, 2014 at 8:45 PM, Stephan Beal wrote:
> on my Pi, so it will be easy to occasionally post updated binaries for
> that platform and the ODroid U3 (i _think_ the binaries might be
> compatible, but haven't tried it). So...
>
Turns out they are: the pi-built binary runs on an odroid:
Hi, all,
last night i scripted the infrastructure to run "almost continuous" builds
using various configuration options on my Pi, so it will be easy to
occasionally post updated binaries for that platform and the ODroid U3 (i
_think_ the binaries might be compatible, but haven't tried it). So...
On Tue, Jul 29, 2014 at 12:46 PM, Stephan Beal
wrote:
> On Tue, Jul 29, 2014 at 6:25 PM, Ron W wrote:
>
>> the push (assuming autosunc isn't pull-only AND the local repo is not
>> no-push).
>>
>
> i didn't know about that option (it's called dont-push, though)
>
>dont-pushPrevent thi
On Tue, Jul 29, 2014 at 7:46 PM, Joerg Sonnenberger wrote:
> fossil descendants?
>
that looks a lot like the timeline output to me:
pi@raspberrypi:/mnt/odroid/fossil/fossil$ f descen
=== 2014-07-16 ===
08:09:43 [e17f7304dd] Update internal tables to Unicode 7.0. (user:
jan.nijtmans tag
fossil test-name-to-id tip
On Tue, Jul 29, 2014 at 1:40 PM, Stephan Beal wrote:
> On Tue, Jul 29, 2014 at 7:37 PM, Stephan Beal
> wrote:
>
>> Limits: only the most basic of unix tools (no perl, etc, but awk would be
>> okay).
>>
>> Assumptions: the repo has at least one checkin (this is for bu
On Tue, Jul 29, 2014 at 07:37:24PM +0200, Stephan Beal wrote:
> i'm looking for a simple, shell-scriptable way to get the tip version uuid
> from a checkout. Currently i've got this beast:
fossil descendants?
Joerg
___
fossil-users mailing list
fossil-u
On Tue, Jul 29, 2014 at 7:37 PM, Stephan Beal wrote:
> Limits: only the most basic of unix tools (no perl, etc, but awk would be
> okay).
>
> Assumptions: the repo has at least one checkin (this is for building
> precompiled binaries of fossil on my ARM devices).
>
this one's not bad:
echo "sel
Hi, all,
i'm looking for a simple, shell-scriptable way to get the tip version uuid
from a checkout. Currently i've got this beast:
pi@raspberrypi:/mnt/odroid/fossil/fossil$ f timeline -type ci -n 1 | sed -n
2p | cut -d'[' -f2 | cut -d']' -f1
e17f7304dd
Limits: only the most basic of unix tools
On Tue, Jul 29, 2014 at 6:25 PM, Ron W wrote:
> the push (assuming autosunc isn't pull-only AND the local repo is not
> no-push).
>
i didn't know about that option (it's called dont-push, though)
dont-pushPrevent this repository from pushing from client to
server.
Thus said Ron W on Tue, 29 Jul 2014 12:25:08 -0400:
> Making autosync default to pull-only would not impact minimize
> unintentional forks.
Actually, it would. Consider this scenario.
Tizio clones and uses default autosync.
Caglio clones and enabled pull-only.
Tizio commits something.
C
On Mon, Jul 28, 2014 at 10:10 PM, Andy Bradford
wrote:
> Thus said Baruch Burstein on Sun, 27 Jul 2014 23:31:17 +0300:
> > Maybe this should be the default always, even if I have write
> > permission, in order to prevent accidental pushes?
>
> I believe changing the default for autosyn
On Tue, Jul 29, 2014 at 5:10 AM, Andy Bradford
wrote:
> > When cloning a repository, if I don't have write privileges, can
> > autosync by default be set to "pullonly" in the clone, to prevent
> > annoying "pull only - not authorized to push"?
>
> Are you suggesting that the clone dete
14 matches
Mail list logo
