On 6/17/2016 5:33 PM, Scott Robison wrote:
On Fri, Jun 17, 2016 at 6:04 PM, Warren Young > wrote:
For any blob data that Fossil considers “text,” why not strip all
CRs on ingest, then based on either a setting or platform check
inject
On Fri, Jun 17, 2016 at 6:04 PM, Warren Young wrote:
> On Jun 17, 2016, at 1:59 PM, Scott Robison
> wrote:
> >
> > Would it be a bad thing to just settle on LF only going forward, always
> stripping CR?
>
> The argument over canonicalizing all text
On Jun 17, 2016, at 1:59 PM, Scott Robison wrote:
>
> Would it be a bad thing to just settle on LF only going forward, always
> stripping CR?
The argument over canonicalizing all text input to LF has been had here before
— with me as at least one of its proponents —
On Fri, Jun 17, 2016 at 1:53 PM, Warren Young wrote:
> While trying to replicate the problem reported in another thread,[1] I
> noticed an odd behavior. If I edit a comment via fossil ui, then pull the
> change and try to edit it locally with fossil amend, Vim shows ^M
>
While trying to replicate the problem reported in another thread,[1] I noticed
an odd behavior. If I edit a comment via fossil ui, then pull the change and
try to edit it locally with fossil amend, Vim shows ^M characters at the end of
every line, implying that Fossil UI has transformed the LF
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
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
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,
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:
Push to file://E:/db/xxx.fossil
Round-trips: 1 Artifacts sent: 0 received: 0
Push done, sent: 281962 received: 12407
9 matches
Mail list logo