From: "J. Bruce Fields" <bfields@fieldses.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: user-manual patches
Date: Sun, 26 Aug 2007 12:20:50 -0400 [thread overview]
Message-ID: <20070826162050.GA28795@fieldses.org> (raw)
On Sun, Aug 26, 2007 at 12:16:56PM -0400, J. Bruce Fields wrote:
>
> The following changes are available from the "maint" branch at:
>
> ssh://linux-nfs.org/~bfields/exports/git.git maint
Um, sorry for the duplicates. I'm clearly not competent to operation
git-send-email.
Also one chunk from David Kastrup's gitlink fixes only applied to
master, so I applied the whole thing there, did a merge, and pushed the
result to my master branch. If that was the right thing to do, then I
guess you can just pull from both of
git://linux-nfs.org/~bfields/git maint
git://linux-nfs.org/~bfields/git master
?
--b.
next reply other threads:[~2007-08-26 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-26 16:20 J. Bruce Fields [this message]
2007-08-26 21:26 ` user-manual patches Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2007-08-26 16:16 J. Bruce Fields
2007-08-26 16:16 J. Bruce Fields
2007-05-14 15:20 J. Bruce Fields
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=20070826162050.GA28795@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).