From: Junio C Hamano <junkio@cox.net>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: Comments in read-tree about #nALT
Date: Sat, 27 Aug 2005 22:46:06 -0700 [thread overview]
Message-ID: <7vd5nypqap.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0508271709530.23242@iabervon.org> (Daniel Barkalow's message of "Sat, 27 Aug 2005 17:57:29 -0400 (EDT)")
Daniel Barkalow <barkalow@iabervon.org> writes:
> I'd actually like to introduce Documentation/technical/trivial-merge for
> this stuff; I think it would be good to have documentation for people who
> need to know how the stuff works, rather than just how to use it, so we
> get a balance between reams of information that users don't want to wade
> through and being too vague for future developers.
I think that is an excellent idea to have user manual vs
internals manual.
prev parent reply other threads:[~2005-08-28 5:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-27 6:07 Comments in read-tree about #nALT Daniel Barkalow
2005-08-27 7:08 ` Junio C Hamano
2005-08-27 8:59 ` Junio C Hamano
2005-08-27 21:57 ` Daniel Barkalow
2005-08-27 23:15 ` Daniel Barkalow
2005-08-27 23:35 ` Linus Torvalds
2005-08-28 0:16 ` Daniel Barkalow
2005-08-28 1:18 ` Linus Torvalds
2005-08-30 0:42 ` Junio C Hamano
2005-08-30 0:58 ` Linus Torvalds
2005-08-28 5:45 ` Junio C Hamano
2005-08-28 5:46 ` Junio C Hamano [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=7vd5nypqap.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.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 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.