If anybody is interested in writing some architecture docs, that's
great, but I don't particularly want to do it :-).
If someone does, I'll answer questions. Also George Nachman has a couple
of UML diagrams at the end of which may be handy:
http://code.google.com/p/iterm2/wiki/TmuxIntegration
Al
On Tue, Feb 19, 2013 at 6:22 PM, Nicholas Marriott <
nicholas.marri...@gmail.com> wrote:
> Also I
> think tmux docs are not the place to tell people about using source
> control tools, it's a distraction for the people who just want to use
> tmux.
>
I agree with that. The line is pretty blurry be
On Tue, Feb 19, 2013 at 06:11:18PM -0500, Richard Woodbury wrote:
>On Tue, Feb 19, 2013 at 1:23 PM, Nicholas Marriott
><[1]nicholas.marri...@gmail.com> wrote:
>
> The NOTES file already says that code contributions should come to
> mailing list by email.
>
>Yes, but it doesn
On Tue, Feb 19, 2013 at 1:23 PM, Nicholas Marriott <
nicholas.marri...@gmail.com> wrote:
> The NOTES file already says that code contributions should come to
> mailing list by email.
Yes, but it doesn't specify a preference for attached vs. inline. If there
is no preference, may it is fine the w
The NOTES file already says that code contributions should come to
mailing list by email. And it is already linked to under "Release
Notes" from the website.
So far we've had one person enquiring about this - and he still managed
to do it just fine. I don't think we need any extra documentation,
p
On Tue, Feb 19, 2013 at 2:13 AM, Thomas Adam wrote:
> I did have a few notes on this once regarding the correct "policy" for
> contributors; perhaps I will add a sentence about this to the NOTES
> file.
>
I might also suggest creating a "Development" link on
http://tmux.sourceforge.net, perhaps
On Tuesday, February 19, 2013 at 12:46 AM, Nicholas Marriott wrote:
> Hi
>
> tmux doesn't use GitHub, it is on SourceForge.
>
> I want one central point for reviewing and discussing code changes and
> the best is the mailing list. Particularly since we may need to apply
> stuff to OpenBSD CVS bef
Hi
tmux doesn't use GitHub, it is on SourceForge.
I want one central point for reviewing and discussing code changes and
the best is the mailing list. Particularly since we may need to apply
stuff to OpenBSD CVS before or as well as SourceForge.
I don't see how it is difficult, you don't have to
On 19 February 2013 04:34, Aaron Jensen wrote:
> I know you all have decided to explicitly not accept pull requests via
> github, but I'm curious why? I just submitted a patch via send-email and it
Git isn't the primary VCS in use; nor is it integral to the workflow.
Its use is to make contributi
