On Feb 9, 2016, at 1:53 PM, Richard Hipp wrote:
>
> Would it be easier if you configured your server to allow your 160+
> students to clone/push/pull using HTTP? The HTTP protocol is built
> into Fossil and is thus much less sensitive to the idiosyncrasies of
> individual SSH
On Feb 9, 2016, at 5:50 AM, Stephan Beal wrote:
>
> Can you post the configure/build options you used?
Well, you kind of nailed it. I’ve reproduced the problem thusly:
f set mv-rm-files 1
f mv foo.c bar.c
f stash
I always enable --with-legacy-mv-rm in my
On Feb 10, 2016, at 9:23 AM, David Mason wrote:
>
> if you use REMOTE_USER in the .ssh/authorized_keys file, you get full
> enforcement of permissions.
Oh, that finally clears something up for me. Someone kept trying to tell me
that SSH keys somehow solved this problem,
On 9 February 2016 at 15:56, Andy Bradford wrote:
> Are you allowing REMOTE_USER to work in your Fossils/dmason.fossil?
>
> $ echo "SELECT * FROM config WHERE name = 'remote_user_ok';" | fossil sql
> -R Fossils/dmason.fossil
>
Bingo! I had actually added this to my
Thus said Ross Berteig on Wed, 10 Feb 2016 15:48:40 -0800:
> which as expected renamed the file in the repository but not on the
> disk. It then says
>
> fossil stash -m "B 2016-02-09"
Did you mean:
fossil stash save -m "B 2016-02-09"
> ERROR: no such file:
Hello All,
Can someone with commit access please review the patch Mr. Young
provided in this post:
http://www.mail-archive.com/fossil-users%40lists.fossil-scm.org/msg22539.html
Is it practical to make a test case for this for code coverage?
Thanks!
On 8 February 2016 at 00:59, Ron Aaron
Thus said Warren Young on Wed, 10 Feb 2016 08:50:29 -0700:
> Also, since the OP talked about permissions, isn't HTTP pretty much
> required?
Yes, and the OP is forcing Fossil to use http over SSH, which means
permissions are enforced.
> As came up in a different recent thread, the
Hi Warren, David,
On 10 February 2016 at 08:57, Warren Young wrote:
> On Feb 10, 2016, at 9:23 AM, David Mason wrote:
>>
>> if you use REMOTE_USER in the .ssh/authorized_keys file, you get full
>> enforcement of permissions.
>
> Oh, that finally clears
On 2/10/2016 7:35 AM, Warren Young wrote:
However, this nonstandard option is not at fault per se. This also triggers it
with a default build:
mv foo.c bar.c
f mv --soft foo.c bar.c
f stash
So, the problem is trying to stash a renamed file.
Given this nice, concise, and
On Feb 10, 2016, at 4:48 PM, Ross Berteig wrote:
>
> What was fossil stash supposed to do in this circumstance?
OP expects the stash to be as capable as bundles, differing only in where the
archived data are stored and how each archive is named. (Stash IDs vs bundle
10 matches
Mail list logo