Proposal: Output should push to different servers in parallel
I experienced a slowdown in Git pushing when I push to more than one server. I propose: Run push to several servers in parallel. Not to mix the output, nevertheless serialize the output, that is for example cache the output of the second server push and start to output it immediately after the first server push is finished. This approach combines the advantages of the current way (I suppose it is so) to serialize pushes: first push to the first server, then to the second, etc. and of my idea to push in parallel. I think the best way would be use multithreading, but multiprocessing would be a good quick solution.
Feature suggestion: Filter branches by user
I want Git to display all branches created by me.
So we need the new feature of Git, to display all branches created by a
given user ("me" by default).
I think, the similar feature for tags may also be useful.
Bug report: stdout vs stderr
Why half of Git output goes to stdout and half to stderr? I suspect this is a bug. Below I call `git pushbug` alias defined it the below presented config file. $ cat .git/config [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = g...@bitbucket.org:portonv/algebraic-general-topology.git fetch = +refs/heads/*:refs/remotes/origin/* pushurl = g...@github.com:vporton/algebraic-general-topology.git pushurl = g...@bitbucket.org:portonv/algebraic-general- topology.git [gui] wmstate = normal geometry = 1680x957+0+27 189 177 [alias] pushbug = !git push && git checkout prerelease && git merge master && git push && git checkout devel && git merge prerelease && git push && git checkout master [branch "master"] remote = origin merge = refs/heads/master [branch "prerelease"] remote = origin merge = refs/heads/prerelease [branch "devel"] remote = origin merge = refs/heads/devel $ git pushbug 1>$HOME/t/1.txt 2>$HOME/t/2.txt $ cat ~/t/1.txt Your branch is up-to-date with 'origin/prerelease'. Updating ac492a4..c55d1b5 Fast-forward chap-sides.tex | 15 +-- 1 file changed, 13 insertions(+), 2 deletions(-) Your branch is up-to-date with 'origin/devel'. Updating ac492a4..c55d1b5 Fast-forward chap-sides.tex | 15 +-- 1 file changed, 13 insertions(+), 2 deletions(-) Your branch is up-to-date with 'origin/master'. $ cat ~/t/2.txt To g...@github.com:vporton/algebraic-general-topology.git ac492a4..c55d1b5 master -> master To g...@bitbucket.org:portonv/algebraic-general-topology.git ac492a4..c55d1b5 master -> master Switched to branch 'prerelease' To g...@github.com:vporton/algebraic-general-topology.git ac492a4..c55d1b5 prerelease -> prerelease remote: remote: Create pull request for prerelease: remote: https://bitbucket.org/portonv/algebraic-general-topology/pull -requests/new?source=prerelease&t=1 remote: To g...@bitbucket.org:portonv/algebraic-general-topology.git ac492a4..c55d1b5 prerelease -> prerelease Switched to branch 'devel' To g...@github.com:vporton/algebraic-general-topology.git ac492a4..c55d1b5 devel -> devel remote: remote: Create pull request for devel: remote: https://bitbucket.org/portonv/algebraic-general-topology/pull -requests/new?source=devel&t=1 remote: To g...@bitbucket.org:portonv/algebraic-general-topology.git ac492a4..c55d1b5 devel -> devel Switched to branch 'master' -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
A small Git bug
I have three branches: master, prerelease, and devel. Suppose now we are in master. I often run the following command (in fact it is an alias, to save typing): git push && git checkout prerelease && git merge master && git push && git checkout devel && git merge prerelease && git push && git checkout master There is a small problem: After running this command my text editor proposes me to reload changed files. So, it seems that the above command marks some files as changed. It is wrong, because it is inconvenient a little to reload a file or two every time after I submit the changes. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
