Re: [fossil-users] FOSSIL does not push edit comment changes, is this normal?

[Warren Young]

On Jun 17, 2016, at 8:07 AM, Tony Papadimitriou  wrote:
> 
> After editing a couple of check-in comments

How, exactly?  Via fossil ui or fossil amend?

> I did ‘push’ and saw zero artifacts sent.

I just did two edits, one via ui on the remote server and one via amend in the 
local checkout followed by a push, and both edits appear on both sides now.  
This is with

  fossil version 1.36 [63313a5f16] 2016-06-15 15:00:15 UTC
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] FOSSIL does not push edit comment changes, is this normal?

[Tony Papadimitriou]

I tried to reproduce the general sequence of actions on a fresh repo but I 
can't seem to repeat the problem.


However, it does it consistently on my end for this one repo.  I'm keeping a 
'frozen' backup of these two files (local and remote) for future 
investigation, if possible at a later time.  You know, like cryonics ... in 
hopes of finding a future cure :)


So, I guess that's one yet unfortunate test case because I can not possibly 
give it as is with the actual source code content (the comments and other 
peripheral info I do not care about).


Is there some way (via SQL) to delete just the file contents (I only need to 
blank or garble the content for certain file extensions that represent 
proprietary code -- many files) and then I can send you

the repo database so you can check its state, if this might help?

I realize there will be tons of warnings opening the now 'malformed' repo in 
order to attempt the push, but it may still be good enough for you to see 
the problem on your end.  I don't know.
So, if there is a way to obscure the file contents, and I can still 
reproduce it here on the 'dummy' repo files, I'll send them to you for 
examination.
(I suppose this is a somewhat common issue with sharing non-public repos for 
troubleshooting, so maybe you already know of a way to do this.)


-Original Message- 
From: Richard Hipp

Sent: Friday, June 17, 2016 5:15 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] FOSSIL does not push edit comment changes,is 
this normal?


On 6/17/16, Tony Papadimitriou <to...@acm.org> wrote:

This is fossil version 1.35 [3aa86af6aa] 2016-06-14 11:10:39 UTC

After editing a couple of check-in comments, I did ‘push’ and saw zero
artifacts sent.  Here’s the output:

I don’t think this is expected behavior, is it?  If not, what could be the
problem?



It is not expected behavior.  Comment changes should always be pushed.
Do you have a reproducible test case?

--
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users 


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] FOSSIL does not push edit comment changes, is this normal?

[Richard Hipp]

On 6/17/16, Tony Papadimitriou  wrote:
> This is fossil version 1.35 [3aa86af6aa] 2016-06-14 11:10:39 UTC
>
> After editing a couple of check-in comments, I did ‘push’ and saw zero
> artifacts sent.  Here’s the output:
>
> I don’t think this is expected behavior, is it?  If not, what could be the
> problem?
>

It is not expected behavior.  Comment changes should always be pushed.
Do you have a reproducible test case?

-- 
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users