This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
howto-git [2012-11-04 09:32] glen [Pushing big files] |
howto-git [2013-01-20 12:25] glen [Set your configuration] |
||
---|---|---|---|
Line 17: | Line 17: | ||
cd ~/rpm/packages/ | cd ~/rpm/packages/ | ||
./builder -v -bp python-msgpack | ./builder -v -bp python-msgpack | ||
- | =====Set your configuration==== | + | ===== Set your configuration ==== |
Your identity (NOTE: This sets globally): | Your identity (NOTE: This sets globally): | ||
Line 46: | Line 46: | ||
</code> | </code> | ||
+ | when pushing in git-core-1.8.0 ([[http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2012-October/023231.html|reference]]) | ||
+ | <code> | ||
+ | git config --global push.default simple | ||
+ | </code> | ||
=====Download package===== | =====Download package===== | ||
Line 153: | Line 157: | ||
There's exception if you can't do that (is too hard to do due local modifications), you can add the patch filename into ''.bigfiles'' file. See [[http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2012-October/023210.html|pld-devel-en post]]. | There's exception if you can't do that (is too hard to do due local modifications), you can add the patch filename into ''.bigfiles'' file. See [[http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2012-October/023210.html|pld-devel-en post]]. | ||
+ | After you found you pushed and was rejected by big file restriction, you can fix it like this (assuming it was only single commit): | ||
+ | <code bash> | ||
+ | echo 7.3.640 > .bigfiles | ||
+ | git add .bigfiles | ||
+ | git commit --amend | ||
+ | git push origin master | ||
+ | </code> | ||
=====Graphical repository browser===== | =====Graphical repository browser===== | ||