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-10-19 09:28] glen [Adding new key] |
howto-git [2012-11-04 09:31] glen Pushing big files |
||
---|---|---|---|
Line 74: | Line 74: | ||
''master'' branch that tracks remote origin/master branch. | ''master'' branch that tracks remote origin/master branch. | ||
- | =====Commit you changes===== | + | =====Commit your changes===== |
First you put your changes in a staging area - the index: | First you put your changes in a staging area - the index: | ||
git add file | git add file | ||
Line 144: | Line 144: | ||
git branch -a | git branch -a | ||
+ | |||
+ | ===== Pushing big files ===== | ||
+ | |||
+ | You shouldn't (can't) push bigger files than 2MiB. Big files, including patches, should be stored in distfiles. | ||
+ | |||
+ | If the file is accessible by url, just add ''# SourceX-md5: '' or ''# PatchX-md5: '' comment to the spec, and the file itself does not need to be added to git index. remove/revert if you already did. | ||
+ | |||
+ | 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]]. | ||
+ | |||
=====Graphical repository browser===== | =====Graphical repository browser===== |