Re: [fossil-users] --nosync option for merge, update, checkout when disconnected

2016-05-31 Thread Stephan Beal 
On Tue, May 31, 2016 at 11:14 AM, Scott Robison 
wrote:

> DRH: I suspect you never sleep.
>

fwiw, i have never seen him sleep.

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
___
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] --nosync option for merge, update, checkout when disconnected

2016-05-31 Thread Scott Robison 
On Mon, May 30, 2016 at 2:47 PM, John P. Rouillard  wrote:

> In message

Re: [fossil-users] --nosync option for merge, update, checkout when disconnected

2016-05-30 Thread John P. Rouillard 
In message

Re: [fossil-users] --nosync option for merge, update, checkout when disconnected

2016-05-30 Thread Richard Hipp 
On 5/30/16, John P. Rouillard  wrote:
>
> Does it make sense to follow the checkin model for merge/up?
>

Yes it does.

But I'm kinda busy with more urgent matters right this moment.  Do you
have patches?

-- 
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] --nosync option for merge, update, checkout when disconnected

2016-05-30 Thread John P. Rouillard 
Hello Everybody:

I a usually use a central repo with autosync enabled. However
sometimes I want to work from a coffee shop or somewhere else where my
central repo is unavailable.

Similar to what was discussed recently, I need to merge or update my
working area for testing, reporting or just normal work.

Since I am disconnected from my central repo, the pull requests for
merge and update fail and prevent me from using those commands until I
turn off autosync.

While merge/update fail, checkin asks if I want to continue even though the
sync will fail:

  fossil ci --branch test -m "testing checkin"
  Autosync:  http://user@host/fossil/roundup_2
  getaddrinfo() fails: Name or service not known
  Pull done, sent: 0  received: 0  ip:
  Autosync failed.
  continue in spite of sync failure (y/N)?

If I say yes, the checkin to my local repo works.

Does it make sense to follow the checkin model for merge/up?

Alternatively is there some argument I can use for the "pulling"
commands. E.G. a hypothetical --nosync option to turn:

  $ fossil up jquery_1.12.4_upgrade
  Autosync:  http://user@host/fossil/roundup_2
  getaddrinfo() fails: Name or service not known
  Pull done, sent: 0  received: 0  ip:
  Autosync failed.
  Cannot proceed with update

into:

  $ fossil up --nosync jquery_1.12.4_upgrade
  REMOVE fo
  --
  updated-to:   
  changes:  1 file modified.
  "fossil undo" is available to undo changes to the working checkout.

While I can use 'fossil settings autosync 0' there is a good chance I
will forget to turn it on and not notice the next time I up/merge.

Suggestions?

AtDhVaAnNkCsE

--
-- rouilj
John Rouillard
===
My employers don't acknowledge my existence much less my opinions.


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