-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 14/09/14 09:06 PM, Peter Stuge wrote: > Rich Freeman wrote: >> If you just want to do 15 standalone commits before you push you >> can do those sequentially easily enough. A branch would be more >> appropriate for some kind of mini-project. > .. >> That is the beauty of git - branches are really cheap. So are >> repositories > > And commits. > > Not only are branches cheap, they are also very easy to create, > and maybe most importantly they can be created at any time, even > after the commits. > > It's quick and painless to create a bunch of commits which aren't > really closely related in sequence, and only later clean the whole > series of commits up while creating different branches for commits > which should actually be grouped rather than mixed all together. >
Ahh, so the secret here would then be just to git add files on a related per-package basis, leaving the other files out of the commit. that makes sense. There would still be the issue of untracked files in the repo and the ability to switch back to the 'master' branch to cherry-pick a commit for pushing, though... I guess we'd just have to deal with the delay there and try and push all of the changes at once? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlQXJQkACgkQ2ugaI38ACPBFBQD/Z1SYvajcf/WORxknJGu1VfI0 f8CFhMTdE34Bk0Zd+GoA/iJtwsYBUQQHXhRjs7AzQDxaIEuFRgzyUgee4BICKaiq =8fbP -----END PGP SIGNATURE-----
