From: James Cloos <cloos@jhcloos.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: keeping remote repo checked out?
Date: Wed, 30 Nov 2005 20:15:58 -0500 [thread overview]
Message-ID: <m38xv5r50x.fsf@lugabout.cloos.reno.nv.us> (raw)
In-Reply-To: <7vbr051ad1.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Sun, 27 Nov 2005 23:48:26 -0800")
>>>>> "Junio" == Junio C Hamano <junkio@cox.net> writes:
Junio> Creative use of hooks/post-update would solve that.
I'll have to look into that.
Junio> However, you should be very careful if you sometimes edit on
Junio> server and sometimes push from other machine to the server on
Junio> the same branch on the server.
I always pull before editing on the laptop....
Thanks,
-JimC
--
James H. Cloos, Jr. <cloos@jhcloos.com>
next prev parent reply other threads:[~2005-12-01 2:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 7:13 keeping remote repo checked out? James Cloos
2005-11-28 7:48 ` Junio C Hamano
2005-11-28 10:57 ` Petr Baudis
2005-11-28 19:35 ` Junio C Hamano
2005-11-28 21:28 ` Petr Baudis
2005-11-28 21:46 ` Junio C Hamano
2005-11-28 22:26 ` Linus Torvalds
2005-11-29 0:19 ` Daniel Barkalow
2005-11-29 0:43 ` Linus Torvalds
2005-11-29 2:35 ` Daniel Barkalow
2005-11-29 2:39 ` Linus Torvalds
2005-11-29 3:40 ` [PATCH] " Daniel Barkalow
2005-11-29 4:34 ` Linus Torvalds
2005-11-29 6:02 ` Daniel Barkalow
2005-11-29 6:38 ` Junio C Hamano
2005-11-29 6:57 ` Daniel Barkalow
2005-11-29 7:52 ` Junio C Hamano
2005-11-29 13:39 ` Matthias Urlichs
2005-11-29 17:31 ` Junio C Hamano
2005-11-29 17:22 ` Daniel Barkalow
2005-11-29 19:28 ` Junio C Hamano
2005-11-29 21:44 ` Daniel Barkalow
2005-11-29 12:14 ` Matthias Urlichs
2005-12-01 1:15 ` James Cloos [this message]
2005-12-01 2:43 ` 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=m38xv5r50x.fsf@lugabout.cloos.reno.nv.us \
--to=cloos@jhcloos.com \
--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).