On Wed, Oct 15, 2014 at 12:04 AM, Andy Bradford amb-fos...@bradfords.org
wrote:
Thus said David Mason on Tue, 14 Oct 2014 23:27:38 -0400:
If I had my ideal, it would be to have a setting like ssh-clone-id
that could be set (in the remote repo) to -local-, -remote-, or
anything else,
Thus said David Mason on Fri, 10 Oct 2014 09:14:48 -0400:
So the student would do:
fossil clone -A student1 ssh://xxx@remote.machine/student1.fossil
srepo.fossil
Just a quick question regarding this particular setup. Clearly you are
using a shared SSH account in which all your fossils
On 14 October 2014 23:01, Andy Bradford
amb-sendok-1415934068.lbncfdeapmpipjbdl...@bradfords.org wrote:
Thus said David Mason on Fri, 10 Oct 2014 09:14:48 -0400:
So the student would do:
fossil clone -A student1 ssh://xxx@remote.machine/student1.fossil
srepo.fossil
Just a quick
Thus said David Mason on Tue, 14 Oct 2014 23:27:38 -0400:
If I had my ideal, it would be to have a setting like ssh-clone-id
that could be set (in the remote repo) to -local-, -remote-, or
anything else, and in the anything-else case it would use that.
I had actually considered something
On Mon, Oct 13, 2014 at 3:58 AM, David Mason dma...@ryerson.ca wrote:
Yeah shunning is a really big stick. If I understand it correctly, if
you ever shunned a 0-length file, you would never be able to commit a
zero-length file again!
Er that's an excellent point. Perhaps we need to
On Oct 13, 2014 7:42 AM, David Mason dma...@ryerson.ca wrote:
On 13 October 2014 04:54, Tony Papadimitriou to...@acm.org wrote:
The claim that once you shun a 0-length file you will not be able to
commit another 0-length file again is not entirely true. If you first
delete the existing
On Mon, Oct 13, 2014 at 6:44 PM, Scott Robison sc...@casaderobison.com
wrote:
On Oct 13, 2014 7:42 AM, David Mason dma...@ryerson.ca wrote:
pointing out what a big stick this was. Perhaps pointing out this
edge-case in the documentation or the shunning web page would be
sufficient (or a
On Sun, Oct 12, 2014 at 9:58 PM, David Mason dma...@ryerson.ca wrote:
Yeah shunning is a really big stick.
Probably better to quarantine than to auto-shun Any content flagged as
quarantined could be reviewed, then any that's truly spam shunned. (Any
illegal (or otherwise illegitimate) may be
On Sat, Oct 11, 2014 at 11:25 PM, David Mason dma...@ryerson.ca wrote:
I'm still digging around in the code, trying to grok all this.
Presumably there can be multiple manifests in a sync (or push) because
there could be multiple commits without a push, and then they would
all be presented at
On 12 October 2014 06:06, Richard Hipp d...@sqlite.org wrote:
No such luck. The artifacts are present in an arbitrary order. It is
entirely possible that a push might involve multiple server round-trips
and that the firrst server round-trip might send artifacts from later
check-ins while
On Sun, Oct 12, 2014 at 10:53 AM, David Mason dma...@ryerson.ca wrote:
On 12 October 2014 06:06, Richard Hipp d...@sqlite.org wrote:
No such luck. The artifacts are present in an arbitrary order. It is
entirely possible that a push might involve multiple server round-trips
and that the
On 12 October 2014 13:59, Richard Hipp d...@sqlite.org wrote:
The shun mechanism is really intended only to remove spam or illegal
content.
Yeah shunning is a really big stick. If I understand it correctly, if
you ever shunned a 0-length file, you would never be able to commit a
zero-length
On Sat, Oct 11, 2014 at 5:36 AM, David Mason dma...@ryerson.ca wrote:
Seems a bit weird, but OK... so how do I find out which of the
artifacts was a manifest... and does this mean I can't have a file in
the repo called manifest ?
Section 1.0 of the link you quoted hints at the answer:
Any
On Sat, Oct 11, 2014 at 5:36 AM, David Mason dma...@ryerson.ca wrote:
Seems a bit weird, but OK... so how do I find out which of the
artifacts was a manifest...
To elaborate a bit on the question is this blob a checkin record...
There is actually only one table in fossil which can
I'm still digging around in the code, trying to grok all this.
Presumably there can be multiple manifests in a sync (or push) because
there could be multiple commits without a push, and then they would
all be presented at once.
I don't suppose I'd be lucky enough that each manifest would be
Some may remember that about a year ago I was trying to get fossil set
up for students in a course. I didn't get it set up then (too much
going on, time pressure, etc.) but I'm doing it now.
I am using the ssh-with-keys-and-forced-commands setup that Andy set
up (thanks!) but one of the things
Oops... sent prematurely..
Some may remember that about a year ago I was trying to get fossil set
up for students in a course. I didn't get it set up then (too much
going on, time pressure, etc.) but I'm doing it now.
I am using the ssh-with-keys-and-forced-commands setup that Andy set
up
On Fri, Oct 10, 2014 at 9:27 AM, David Mason dma...@ryerson.ca wrote:
So the student would do:
fossil clone -A student1 ssh://x...@re.mote/student1.fossil
srepo.fossil
Using a wrapper around Fossil, this form of the clone command could be
automated:
fsl clone URL becomes fossil close -A
On 10 October 2014 10:18, Ron W ronw.m...@gmail.com wrote:
On Fri, Oct 10, 2014 at 9:27 AM, David Mason dma...@ryerson.ca wrote:
So the student would do:
fossil clone -A student1 ssh://x...@re.mote/student1.fossil
srepo.fossil
Using a wrapper around Fossil, this form of the clone
On Fri, Oct 10, 2014 at 2:42 PM, David Mason dma...@ryerson.ca wrote:
Yes, but the client side is on their own laptop or whatever, so no
opportunity to wrap.
So, you aren't providing a zip file of standardized tools for the class?
That's what has happened for every class I've taken that
20 matches
Mail list logo
