From: greened@obbligato.org (David A. Greene)
To: Jan <jk@jk.gs>
Cc: git@vger.kernel.org
Subject: Re: git-subtree Ready for Inspection
Date: Wed, 08 Feb 2012 23:02:44 -0600 [thread overview]
Message-ID: <87liocoayz.fsf@smith.obbligato.org> (raw)
Jan <jk@jk.gs> writes:
> On 02/08/2012 04:49 AM, David A. Greene wrote:
>> I've put up a branch containing git-subtree at:
>>
>> gitolite@sources.obbligato.org:git.git
>
> A publicly accessible URL would be much more helpful. :-)
Do you mean running gitweb? Are you not able to access the above
repository? I can do that if it makes things easier but it will take a
bit of time.
-Dave
next reply other threads:[~2012-02-09 5:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 5:02 David A. Greene [this message]
2012-02-09 5:17 ` git-subtree Ready for Inspection Nazri Ramliy
2012-02-09 21:52 ` David A. Greene
2012-02-09 10:07 ` Jakub Narebski
2012-02-09 12:39 ` Matthieu Moy
-- strict thread matches above, loose matches on Subject: below --
2012-02-08 3:49 David A. Greene
2012-02-08 12:35 ` Jan Krüger
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=87liocoayz.fsf@smith.obbligato.org \
--to=greened@obbligato.org \
--cc=git@vger.kernel.org \
--cc=jk@jk.gs \
/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).