https://bugzilla.redhat.com/show_bug.cgi?id=1021342 --- Comment #26 from Pete Travis <me@xxxxxxxxxxxxxx> --- (In reply to TianShixiong from comment #25) > > I found the problem easily enough from your description, so no worries. The > > only part you missed was that `git format-patch ...` creates some .patch > > files in the working directory that you can then share via email or bz. > > I did that, but didn't know it would generate a patch file. Now it's > attached. :) > > Do I still need 'git push' after 'checkout'? There's no need to `git push` with this method; whoever accepts the patch can do that part for you. However, members of the "docs-writers" FAS group (which I believe you are) can skip the branch-patch sequence, commit directly to the source repo and `git push` their commit. Either way is fine, that's up to you. Whether you commit directly or submit patches, it is a good idea to communicate with the others working on the guide so the work doesn't overlap, strings can get repushed to tx, etc. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. -- relnotes-content mailing list relnotes-content@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/relnotes-content
