From: Shourya Shukla <shouryashukla.oo@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, sandals@crustytoothpaste.net,
Shourya Shukla <shouryashukla.oo@gmail.com>
Subject: [PATCH v3 0/4] gitfaq: add issues in the 'Common Issues' section
Date: Tue, 21 Apr 2020 18:41:08 +0530 [thread overview]
Message-ID: <20200421131111.29201-1-shouryashukla.oo@gmail.com> (raw)
This is the third version of addition of issues in the 'Common Issues' section.
In this version I have:
1. Changed column wrapping from 90 col. to ~70 col.
2. Removed the issues: 'rebasing-and-merging' & 'checking-out'
3. Added issue: 'shallow-cloning'
4. Separated the issues in individual commits.
5. Corrected spelling and grammatical mistakes.
I decided to drop the issues mentioned in (2) because of the lack of clarity
in them. As Junio advised, it would be better to improve their respective
documentations rather than adding them in the FAQ.
I really appreciate Junio and Brian for reviewing my patch in such great detail :)
Regards,
Shourya Shukla
Shourya Shukla (4):
gitfaq: files in .gitignore are tracked
gitfaq: changing the remote of a repository
gitfaq: shallow cloning a repository
gitfaq: fetching and pulling a repository
Documentation/gitfaq.txt | 86 ++++++++++++++++++++++++++++++++++++++++
1 file changed, 86 insertions(+)
--
2.20.1
next reply other threads:[~2020-04-21 13:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 13:11 Shourya Shukla [this message]
2020-04-21 13:11 ` [PATCH v3 1/4] gitfaq: files in .gitignore are tracked Shourya Shukla
2020-04-21 13:11 ` [PATCH v3 2/4] gitfaq: changing the remote of a repository Shourya Shukla
2020-04-21 13:11 ` [PATCH v3 4/4] gitfaq: fetching and pulling " Shourya Shukla
2020-04-21 13:12 [PATCH v3 0/4] gitfaq: add issues in the 'Common Issues' section Shourya Shukla
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 \
--in-reply-to=20200421131111.29201-1-shouryashukla.oo@gmail.com \
--to=shouryashukla.oo@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sandals@crustytoothpaste.net \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).