From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Emily Shaffer <emilyshaffer@google.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH 1/1] docs: add a FAQ
Date: Mon, 16 Mar 2020 00:13:29 +0000 [thread overview]
Message-ID: <20200316001329.GB6910@camp.crustytoothpaste.net> (raw)
In-Reply-To: <xmqqa74h9oqd.fsf@gitster.c.googlers.com>
[-- Attachment #1: Type: text/plain, Size: 2587 bytes --]
On 2020-03-15 at 23:34:34, Junio C Hamano wrote:
> "brian m. carlson" <sandals@crustytoothpaste.net> writes:
>
> > Note that the long lines for certain questions are required, since
> > Asciidoctor does not permit broken lines there.
>
> I didn't see "long lines", but was puzzled by a few lines with
> ununiform indentation.
I'll fix all that. Apparently somewhere along the line my editor got
confused and inserted two spaces (which is my typical AsciiDoc
configuration) instead of a tab (which is what I've configured for Git
files).
> > +Common Issues
> > +-------------
> > +
> > +[[last-commit-amend]]
> > +I've made a mistake in the last commit. How do I change it?::
> > + You can make the appropriate change to your working tree, run `git add <file>`
> > + to stage it, and then `git commit --amend`. Your change will be included in
> > + the commit, and you'll be prompted to edit the commit message again; if you
> > + don't want to edit it, you can use the `--no-edit` option to `git commit` in
> > + addition, or just save and quit when your editor opens.
>
> When the undesired part of the last change was "I added a junk
> file", then instead of `git add`, `git rm [--cached]` would become
> necessary.
Good point. I'll mention `git add` or `git rm` as appropriate.
> I personally would prefer to say "if you want to use the original
> commit message verbatim" instead of "you do not want to edit", but
> it may be just me. I just find the document to give more positive
> attitude if it avoids phrasing end-users' wishes in terms of what
> they do not want to do.
Thanks. This is great feedback.
> > +[[undo-previous-change]]
> > +I've made a change with a bug and it's been included in the main branch. How should I undo it?::
> > + The usual way to deal with this is to use `git revert`. This preserves the
> > + history that the original change was made and was a valuable contribution, but
> > + also introduces a new commit that undoes those changes because the original
> > + had a problem. The commit message of the revert indicates the commit which
> > + was reverted and can be edited to include an explanation as to why the revert
> > + was made.
>
> Can we phrase "and can be edited" in a bit more opinionated way?
> The users are encouraged to describe why and that is why we open an
> editor by default for them to do so.
Yes, I agree that we want to encourage a helpful commit message here. Will update.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2020-03-16 0:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-15 22:39 [PATCH 0/1] FAQ for common user questions brian m. carlson
2020-03-15 22:39 ` [PATCH 1/1] docs: add a FAQ brian m. carlson
2020-03-15 23:34 ` Junio C Hamano
2020-03-16 0:13 ` brian m. carlson [this message]
2020-03-18 23:00 ` Emily Shaffer
2020-03-19 0:09 ` Junio C Hamano
2020-03-19 23:49 ` brian m. carlson
2020-03-19 17:02 ` Shourya Shukla
2020-03-19 23:31 ` brian m. carlson
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=20200316001329.GB6910@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).