From: demerphq <demerphq@gmail.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Git <git@vger.kernel.org>, David Kastrup <dak@gnu.org>,
Vincent van Ravesteijn <vfr@lyx.org>,
Francis Stephens <francisstephens@gmail.com>
Subject: Re: Confusing git log --- First time bug submission please advise on best practices
Date: Fri, 7 Feb 2014 19:37:40 +0800 [thread overview]
Message-ID: <CANgJU+UcONQYAQ7K-_W7H_12JhfG+iuqYAU81xYMc5kLPXwn_Q@mail.gmail.com> (raw)
In-Reply-To: <20140207102619.GA27616@lanh>
On 7 February 2014 18:26, Duy Nguyen <pclouds@gmail.com> wrote:
> On Fri, Feb 07, 2014 at 09:43:46AM +0000, Francis Stephens wrote:
>> Thanks for your clear response. I can see where I went wrong now.
>
> Maybe something like this would help avoid confusion a bit in the
> future? This toy patch puts a horizontal line as a break between two
> commits if they are not related, so we can clearly see linear commit
> segments.
FWIW, this would have saved a lot of head scratching at work over the years.
I'd love to see this in place.
Yves
--
perl -Mre=debug -e "/just|another|perl|hacker/"
next prev parent reply other threads:[~2014-02-07 11:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 14:02 Confusing git log --- First time bug submission please advise on best practices Francis Stephens
2014-02-06 16:08 ` Vincent van Ravesteijn
2014-02-06 16:10 ` David Kastrup
2014-02-07 9:43 ` Francis Stephens
2014-02-07 10:26 ` Duy Nguyen
2014-02-07 11:37 ` demerphq [this message]
2014-02-08 13:50 ` [PATCH] log: add --show-linear-break to help see non-linear history Nguyễn Thái Ngọc Duy
2014-03-17 12:51 ` [PATCH v2] log: add --nonlinear-barrier " Nguyễn Thái Ngọc Duy
2014-03-17 19:09 ` Eric Sunshine
2014-03-17 20:32 ` Junio C Hamano
2014-03-18 11:46 ` Duy Nguyen
2014-03-18 19:08 ` Junio C Hamano
2014-03-20 5:44 ` [PATCH v3 1/2] object.h: centralize object flag allocation Nguyễn Thái Ngọc Duy
2014-03-20 5:44 ` [PATCH v3 2/2] log: add --show-linear-break to help see non-linear history Nguyễn Thái Ngọc Duy
2014-03-20 19:15 ` Junio C Hamano
2014-03-21 1:02 ` Duy Nguyen
2014-03-25 13:23 ` [PATCH v4 1/2] object.h: centralize object flag allocation Nguyễn Thái Ngọc Duy
2014-03-25 13:23 ` [PATCH v4 2/2] log: add --show-linear-break to help see non-linear history Nguyễn Thái Ngọc Duy
2014-03-25 22:30 ` 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 \
--in-reply-to=CANgJU+UcONQYAQ7K-_W7H_12JhfG+iuqYAU81xYMc5kLPXwn_Q@mail.gmail.com \
--to=demerphq@gmail.com \
--cc=dak@gnu.org \
--cc=francisstephens@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=vfr@lyx.org \
/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).