I think the branch check should only be done when performing a pull
command. That way one can still do ./sync-all fetch, ./sync-all diff, etc
when on a separate branch.
On Sat, Aug 3, 2013 at 9:59 PM, Erik de Castro Lopo mle...@mega-nerd.comwrote:
Erik de Castro Lopo wrote:
Simon
Given the recent debate about using submodules or subtrees, and the
occasional issues with sync-all: did anyone ever look into using the
'repo' tool? Created by Google for Android development (AFAIK), but also
used by several other projects. See https://code.google.com/p/git-repo/
Con:
- It
On Fri, 2013-08-02 at 18:32 +, Simon Peyton-Jones wrote:
Dear ghc-dev friends,
Ian has now officially left Well Typed, so there now isn't anyone
whose day job it is to respond to GHC bug mail, Trac tickets etc.
Well Typed are hiring, and there will be someone new in due course,
but
Better yet, the sync-all script should detect whether it is on master and
error out (with a decent error message) if not.
Why? I think it is behaving properly - it fetches master branch from the server
and merges it into
local master branch, just as expected. I imagine that switching to master
