From: Shourya Shukla <email@example.com> To: firstname.lastname@example.org Cc: email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, Shourya Shukla <email@example.com> Subject: [PATCH 0/2] Add more issues in gitfaq Date: Mon, 6 Apr 2020 23:42:14 +0530 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) I have tried adding more issues and their respective solutions in the gitfaq. Please feel free to point out any mistakes I have made in any sense here. I have tried to add some basic questions such as difference between rebasing and merging, changing remote, etc. I intend to add even more changes in the further patches. Also, one thing I wanted to ask is whether I should add a sort of guide section to configuring 'send-email' and a using 'format-patch'. Although there does exist a man page for the same but I thought that a simpler and all at one place version could be made. One suggestion I have is that we should have an INDEX/CONTENTS section in this guide because the end user may not know whether solution to a particular problem exists here or not. Regards, Shourya Shukla Shourya Shukla (2): gitfaq: cleanup gitfaq.txt gitfaq: append the 'Common Issues' section Documentation/gitfaq.txt | 182 +++++++++++++++++++++++++++------------ 1 file changed, 127 insertions(+), 55 deletions(-) -- 2.20.1
next reply other threads:[~2020-04-06 18:12 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-06 18:12 Shourya Shukla [this message] 2020-04-06 18:12 ` [PATCH 1/2] gitfaq: cleanup gitfaq.txt Shourya Shukla 2020-04-06 19:06 ` Junio C Hamano 2020-04-06 23:46 ` Junio C Hamano 2020-04-07 1:07 ` brian m. carlson 2020-04-07 3:15 ` Junio C Hamano 2020-04-08 18:22 ` Pratyush Yadav 2020-04-10 18:29 ` Junio C Hamano 2020-04-06 18:12 ` [PATCH 2/2] gitfaq: append the 'Common Issues' section Shourya Shukla 2020-04-06 19:28 ` Junio C Hamano
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH 0/2] Add more issues in gitfaq' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).