From: Shourya Shukla <shouryashukla.oo@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, sandals@crustytoothpaste.net,
emilyshaffer@google.com, martin.agren@gmail.com,
Shourya Shukla <shouryashukla.oo@gmail.com>
Subject: [PATCH v2 0/1] update gitfaq
Date: Mon, 13 Apr 2020 19:39:17 +0530 [thread overview]
Message-ID: <20200413140918.4778-1-shouryashukla.oo@gmail.com> (raw)
Hello,
Thank you Junio and Brian for reviewing my patch :)
https://lore.kernel.org/git/20200406181216.5340-1-shouryashukla.oo@gmail.com/
The changes in this version are:
1. Dropped the gitfaq cleanup patch.
2. Improved the 'rebasing and merging' section. Added information on when to rebase/merge.
3. Improved the 'files-in-.gitignore-are-tracked' section. Added significance of `git add` & `git status`.
4. Improved the 'checking-out' section. Added more description in use cases of `git checkout` as well as introduced
`git switch` and `git restore`.
5. Improvements in sentence formation and the terms used.
Regards,
Shourya Shukla
Shourya Shukla (1):
gitfaq: append the 'Common Issues' section
Documentation/gitfaq.txt | 104 +++++++++++++++++++++++++++++++++++++++
1 file changed, 104 insertions(+)
--
2.20.1
next reply other threads:[~2020-04-13 14:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 14:09 Shourya Shukla [this message]
2020-04-13 14:09 ` [PATCH v2 1/1] gitfaq: append the 'Common Issues' section Shourya Shukla
2020-04-14 1:06 ` brian m. carlson
2020-04-14 7:33 ` Junio C Hamano
2020-04-16 19:05 ` Junio C Hamano
2020-04-21 6:58 ` Shourya Shukla
2020-04-16 19:36 ` Junio C Hamano
2020-04-21 0:57 ` Junio C Hamano
2020-04-21 8:38 ` Shourya Shukla
2020-04-21 18:00 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2020-04-13 10:55 [PATCH v2 0/1] update gitfaq 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200413140918.4778-1-shouryashukla.oo@gmail.com \
--to=shouryashukla.oo@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=martin.agren@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).