From: Junio C Hamano <junkio@cox.net>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] stgit: allow spaces in filenames
Date: Wed, 13 Jul 2005 15:26:39 -0700 [thread overview]
Message-ID: <7vpstms5pc.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <1121290004.6876.11.camel@localhost.localdomain> (Catalin Marinas's message of "Wed, 13 Jul 2005 22:26:44 +0100")
Catalin Marinas <catalin.marinas@gmail.com> writes:
>> I'd very much like to stay on the same list. By the same logic, cogito
>> should have it's own list as well...
>
> I'd like this too and it's probably OK with a low traffic (we'll see if
> we receive complaints :-) ).
I'd like to keep Porcelain discussions on this list for two
reasons:
(1) Porcelain implementations need their own bookkeeping
information somewhere, and possibly in .git/ directory.
I'd want to see them agree on what's stored where for what
purpose and stay compatible when that makes sense. The
place to brew that concensus is here.
(2) The core GIT people want to learn what Porcelain needs
from the core. I am personally interested in StGIT so
subscribing to that list is fine for me, but it is
convenient to have everything in one place, especially with
this relatively low traffic.
next prev parent reply other threads:[~2005-07-14 18:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 8:38 [PATCH] stgit: allow spaces in filenames Bryan Larsen
2005-07-13 8:38 ` [PATCH] stgit: new --message does not work Bryan Larsen
2005-07-13 10:17 ` [PATCH] stgit: allow spaces in filenames Catalin Marinas
2005-07-13 18:17 ` Bryan Larsen
2005-07-13 21:09 ` Jerry Seutter
2005-07-13 21:26 ` Catalin Marinas
2005-07-13 22:26 ` Junio C Hamano [this message]
2005-07-14 7:02 ` Catalin Marinas
2005-07-14 7:22 ` Bryan Larsen
2005-07-13 16:54 ` Matthias Urlichs
2005-07-13 19:51 ` Linus Torvalds
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=7vpstms5pc.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=catalin.marinas@gmail.com \
--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.