From: Stephen & Linda Smith <ischis2@cox.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] How to keep a project's canonical history correct.
Date: Fri, 09 May 2014 21:01:46 -0700 [thread overview]
Message-ID: <4639676.GfT2sDDHtN@thunderbird> (raw)
In-Reply-To: 1399615721-566-1-git-send-email-ischis2@cox.net
On Friday, May 09, 2014 02:05:44 PM Junio C Hamano wrote:
> I needed a few tweaks on top while queuing. You will find the
> result on 'pu' after I push it out.
>
> In addition to one typofix ("because" lacking "c"), here are what I
> did:
>
> - Typeset concrete command e.g. `git pull` in monospace.
>
> - The second and subsequent paragraphs continued with "+" need to
> be flushed to the left; leaving them indented will format them in
> monospace (see "with `git pull --rebase` or something").
>
> - Be more explicit in describing 'trunk' being 'the first-parent
> chain' in the text.
>
> - Refer to a newer article that discusses this exact topic.
>
> - De-emphasize 'fix-bug-12345' in "Merge fix-bug-12345" log message.
>
> - Describe what the final history illustration shows.
>
>
> Unless you have objections to the below (or suggestions for better
> alternatives), there is no need to resend the patch.
>
I like the changes.
prev parent reply other threads:[~2014-05-10 3:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 15:40 Beginner question on "Pull is mostly evil" Jim Garrison
2014-05-07 16:20 ` David Kastrup
2014-05-07 17:04 ` Jeff King
2014-05-07 20:15 ` Junio C Hamano
2014-05-07 20:30 ` Jim Garrison
2014-05-07 20:51 ` Junio C Hamano
2014-05-08 0:45 ` Stephen & Linda Smith
2014-05-09 6:08 ` [PATCH] How to keep a project's canonical history correct Stephen P. Smith
2014-05-09 13:41 ` Stephen Smith
2014-05-09 21:05 ` Junio C Hamano
2014-05-10 4:01 ` Stephen & Linda Smith [this message]
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=4639676.GfT2sDDHtN@thunderbird \
--to=ischis2@cox.net \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.