From: Junio C Hamano <junkio@cox.net>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: git@vger.kernel.org
Subject: Re: How to create and keep up to date a naked/bare repository?
Date: Fri, 27 Jan 2006 13:00:11 -0800 [thread overview]
Message-ID: <7vek2t1j50.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 20060127190157.GF23949@fieldses.org
"J. Bruce Fields" <bfields@fieldses.org> writes:
>> Maybe somebody so inclined could copyedit it, find an
>> appropriate place for it somewhere in the tutorial.txt or
>> core-tutorial.txt and feed that back to me in a patch form.
>> Hint, hint,... ;-).
>
> It might make sense just to dump it in Documentation/howto/ for now.
Perhaps, but I forgot to say "after some discussion".
I think people on the list have better suggestion than what I
outlined, and I suspect I probably have some details wrong in
that message.
next prev parent reply other threads:[~2006-01-27 21:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 13:00 [RFD] remembering hand resolve Junio C Hamano
2006-01-25 13:45 ` Andreas Ericsson
2006-01-25 23:56 ` Junio C Hamano
2006-01-26 11:12 ` How to create and keep up to date a naked/bare repository? Mathieu Chouquet-Stringer
2006-01-26 12:22 ` Junio C Hamano
2006-01-26 15:11 ` Mathieu Chouquet-Stringer
2006-01-26 18:27 ` Mathieu Chouquet-Stringer
2006-01-27 3:36 ` Junio C Hamano
2006-01-27 10:30 ` Refs naming after clone (was: Re: How to create and keep up to date a naked/bare repository?) Josef Weidendorfer
2006-01-27 13:34 ` How to create and keep up to date a naked/bare repository? Mathieu Chouquet-Stringer
2006-01-27 18:41 ` Junio C Hamano
2006-01-27 19:01 ` J. Bruce Fields
2006-01-27 21:00 ` Junio C Hamano [this message]
2006-01-29 9:10 ` [PATCH/RFC] git-rerere: reuse recorded resolve Junio C Hamano
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=7vek2t1j50.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=bfields@fieldses.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 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).