Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typo in README #64

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

boghicieusebiu
Copy link

No description provided.

@rlbdv
Copy link
Member

rlbdv commented Sep 17, 2021

Thanks. Would you mind adding a "Signed-off-by:" header to the patch? For the meaning and several ways to add it, see

bup/HACKING

Lines 94 to 117 in d9842e9

Submitting patches
==================
As mentioned, all patches should be posted to the mailing list for
review, and must be "signed off" by the author before official
inclusion (see ./SIGNED-OFF-BY). You can create a "signed off" set of
patches in ./patches, ready for submission to the list, like this:
git format-patch -s -o patches origin/master
which will include all of the patches since origin/master on your
current branch. Then you can send them to the list like this:
git send-email --to bup-list@googlegroups.com --compose patches/*
The use of --compose will cause git to ask you to edit a cover letter
that will be sent as the first message.
It's also possible to handle everything in one step:
git send-email -s --to bup-list@googlegroups.com --compose origin/master
and you can add --annotate if you'd like to review or edit each patch
before it's sent.

@boghicieusebiu
Copy link
Author

I quickly edited the file from github. I haven't used git send-email so far. Feel free to decline the pull request if it does not fit the submitting format.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants