On Sat, Aug 30, 2014 at 10:04:05AM +0200, Gustaf Neumann wrote:

> Here you see the commits:
> 
>     https://bitbucket.org/naviserver/nsoracle/commits/all

Ok, I made some changes to the nsoracle/Makefile, pushed my changes to
my own fork on bitbucket.org, and created a pull request.  You can see
that stuff here:

  
https://bitbucket.org/apiskors/nsoracle/commits/12d73fdae3ac0e0703ff237f77003b441d3ddfd9
  https://bitbucket.org/naviserver/nsoracle/pull-requests

I'm still learning how to actually use Mercurial.  E.g., I originally
cloned my local repository and working copy (on my Linux box) from the
official Naviserver repository above.  My repo remembers that, and so
defaults to trying to push changes back to there, but of course that
fails because I don't have write access.  So instead I explicitly
pushed to my own newly-forked https://bitbucket.org/apiskors/nsoracle
repo, which worked fine.

But should I change my local repo somehow to instead point to my own
fork on Bitbucket?  I'm not sure what the best workflow is with these
tools yet...  Any major recommendations?

One minor annoyance is that "hg log" does not show my entire commit
message.  No big deal, I just have to use "hg -v log" instead, but
that did confuse me for a couple minutes.

-- 
Andrew Piskorski <a...@piskorski.com>

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel

Reply via email to