All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Neal Kreitzinger <nkreitzinger@gmail.com>, git@vger.kernel.org
Subject: Re: who's on first? - following first parent and merge-management
Date: Thu, 8 Mar 2012 01:49:11 -0600	[thread overview]
Message-ID: <20120308074911.GA23712@burratino> (raw)
In-Reply-To: <7vty1zfwmd.fsf@alter.siamese.dyndns.org>

Hi all,

Junio C Hamano wrote:

> Given the above definition, the first thing to realize is that "the
> first parent" is primarily a local concept.
[... and much nice explanation ...]

Would you mind including this explanation as a new file with some name
like <Documentation/howto/using-first-parent.txt>?  I think the quoted
explanation is very clear and I have not come up with any obvious
tweaks to make to it, which is why I am simply suggesting this instead
of sending a patch that would repeat the same text.

Strawman abstract:

| From: Junio C Hamano <gitster@pobox.com>
| Date: Wed, 07 Mar 2012 22:13:46 -0800
| Subject: who's on first? - following first parent and merge-management
| Abstract: In this article, JC describes the "log --first-parent" and
|  "merge --no-ff" options and what kind of history makes them useful.

Hm?
Jonathan

  parent reply	other threads:[~2012-03-08  7:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07  5:36 who's on first? - following first parent and merge-management Neal Kreitzinger
2012-03-07  7:37 ` Junio C Hamano
2012-03-08  6:13   ` Junio C Hamano
2012-03-08  7:14     ` Jeff King
2012-03-08  7:38       ` Junio C Hamano
2012-03-08  8:03       ` Johannes Sixt
2012-03-08 17:30         ` Junio C Hamano
2012-03-09 12:05           ` Holger Hellmuth
2012-03-09 12:29             ` Johannes Sixt
2012-03-09 13:25               ` Holger Hellmuth
2012-03-09 16:26                 ` Junio C Hamano
2012-03-08  7:49     ` Jonathan Nieder [this message]
2012-03-08 22:52       ` 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=20120308074911.GA23712@burratino \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=nkreitzinger@gmail.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.