From: Petr Baudis <pasky@ucw.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: SCSI trees, merges and git status
Date: Tue, 19 Apr 2005 01:28:03 +0200 [thread overview]
Message-ID: <20050418232803.GP5554@pasky.ji.cz> (raw)
In-Reply-To: <7vmzrvsm8j.fsf@assigned-by-dhcp.cox.net>
Dear diary, on Tue, Apr 19, 2005 at 01:23:24AM CEST, I got a letter
where Junio C Hamano <junkio@cox.net> told me that...
> However the "Getting object database" part trashed this symlink
> when I tried to pull from my other repo locally. I am wondering
> it the following might be a better alternative. A possible
> downside in this approach is that you would not pull .git/heads
> and .git/tags (i.e. Pesky stuff) from the remote anymore. Is it
> a problem (I am also CC'ing Petr to hear his opinion on this).
Getting tags is probably nice. You should definitively not get
.git/heads, though. Those are your private stuff mostly, and the HEAD
you "export" is .git/HEAD.
I'm thinking about this yet, since it might be useful to be able to
export multiple branches without needing to set up multiple rsync
URLs... you still don't want the heads/ directory en block, though.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
prev parent reply other threads:[~2005-04-18 23:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 20:28 SCSI trees, merges and git status James Bottomley
2005-04-18 21:39 ` Linus Torvalds
2005-04-18 23:14 ` James Bottomley
2005-04-19 0:03 ` Linus Torvalds
2005-04-19 0:10 ` David Woodhouse
2005-04-19 0:16 ` James Bottomley
2005-04-19 0:41 ` David Woodhouse
2005-04-19 0:13 ` James Bottomley
2005-04-19 0:29 ` Linus Torvalds
2005-04-19 2:17 ` James Bottomley
2005-04-19 3:04 ` Linus Torvalds
2005-04-18 23:23 ` Junio C Hamano
2005-04-18 23:28 ` Petr Baudis [this message]
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=20050418232803.GP5554@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.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).