From: Junio C Hamano <gitster@pobox.com>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: Sean <seanlkml@sympatico.ca>, git@vger.kernel.org
Subject: Re: [PATCH] Add [HOWTO] using merge subtree.
Date: Tue, 08 Jan 2008 19:46:13 -0800 [thread overview]
Message-ID: <7vfxx7psoq.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7vwsqjpyqi.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Tue, 08 Jan 2008 17:35:33 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Miklos Vajna <vmiklos@frugalware.org> writes:
>
> NAK. It may be well intentioned, but it lacks too much context
> to be usable as a generic teaching material.
>
>> +Abstract: In this article, Sean demonstrates how one can use the subtree merge
>> + strategy.
>> +Message-ID: <BAYC1-PASMTP12374B54BA370A1E1C6E78AE4E0@CEZ.ICE>
>> +
>> +How to use the subtree merge strategy
>> +=====================================
>
> Here, before diving to the actual command sequence, you need to
> tell the reader what the objective of the whole exercise is.
Just to avoid discouraging contributors too much, here are
pointers to some other materials in the mailing list archive
that may serve as the basis for the "discussion" section of this
HOWTO.
Side note. I think an ideal HOWTO should
- describe the objective briefly so that the reader can tell if
that is relevant to the task at hand;
- describe the procedure;
- mention other possible avenues and discuss pros and cons, so
that the reader can make an informed decision to employ or not
to employ the solution.
My complaints were that the original had only the second part.
And this message is to give pointers to possible material for
the third part.
* http://thread.gmane.org/gmane.comp.version-control.git/39443
This was the explanation on the way how the initial git-gui
subtree merge was created.
* http://thread.gmane.org/gmane.comp.version-control.git/39963
The introduction of subtree strategy. The original cover letter
and the following discussion is rich with discussions on merge
philosophy and pros and cons.
Back then "submodule" was not available, and we would still
avoid it today in git.git, because use of submodule in a
repository would make the repository non-interoperable with any
clients older than 1.5.2 series (that's one pros-and-cons item).
Somewhere in the thread it was also suggested "am -pN" may be
necessary.
* http://thread.gmane.org/gmane.comp.version-control.git/46569/focus=46609
This is a side note -- it turns out that "am -pN" used on the
context of subtree merge is often not necessary, as --3way is a
magic.
next prev parent reply other threads:[~2008-01-09 3:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1199838182-15178-1-git-send-email-vmiklos@frugalware.org>
2008-01-09 1:35 ` [PATCH] Add [HOWTO] using merge subtree Junio C Hamano
2008-01-09 3:46 ` Junio C Hamano [this message]
2008-01-09 6:28 ` Junio C Hamano
[not found] <1199882097-10420-1-git-send-email-vmiklos@frugalware.org>
2008-01-09 22:33 ` Junio C Hamano
2008-01-15 0:35 ` Miklos Vajna
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=7vfxx7psoq.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=seanlkml@sympatico.ca \
--cc=vmiklos@frugalware.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).