* Strange push/clone errors
@ 2009-03-04 14:01 Tim Visher
2009-03-04 14:39 ` Nicolas Sebrecht
0 siblings, 1 reply; 3+ messages in thread
From: Tim Visher @ 2009-03-04 14:01 UTC (permalink / raw)
To: git
Hello Everyone,
I'm trying to maintain an offline copy of the Git repo for our Sandbox
environment at work and I just came across and oddity in the behavior
I'd expect.
I have a repo on an Internet enabled machine that is a direct clone of
the kernel.org version.
$ git show remote origin
* remote origin
URL: http://www.kernel.org/pub/scm/git/git.git
Remote branch merged with 'git pull' while on branch master
master
Tracked remote branches
html
maint
man
master
next
pu
todo
I then have a repo on a thumb drive that's initially a `clone --bare`
of the repo on the Internet enabled machine. I added that as a remote
on the previously mentioned repo.
$ git remote show sandbox
* remote sandbox
URL: /cygdrive/f/Documents/git.git/
Tracked remote branch
master
When I do a `git push sandbox master` I get the following
$ git push sandbox master
Everything up-to-date
The problem is here. Now that I have a supposedly up to date copy on
my thumb drive, I'd like to be able to push it out to a central server
on our Sandbox network. However, when I do a git clone, tags are
missing.
$ git clone /cygdrive/f/Documents/git.git/
Initialized empty Git repository in /home/tvishe01/Desktop/git/.git/
Checking out files: 100% (1589/1589), done.
$ cd git/
$ git tag
...
v1.6.1.3
v1.6.2-rc0
v1.6.2-rc1
Doing the same thing in the repo connected to kernel.org I get:
$ git tag
v1.6.1.3
v1.6.2
v1.6.2-rc0
v1.6.2-rc1
v1.6.2-rc2
As you can see, v1.6.2 and v1.6.2-rc2 are missing from the repo that
I'm pushing to on my thumb drive, despite it claiming it's up to date.
What am I doing wrong?
Thanks in advance!
--
In Christ,
Timmy V.
http://burningones.com/
http://five.sentenc.es/ - Spend less time on e-mail
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Strange push/clone errors
2009-03-04 14:01 Strange push/clone errors Tim Visher
@ 2009-03-04 14:39 ` Nicolas Sebrecht
2009-03-04 17:37 ` Tim Visher
0 siblings, 1 reply; 3+ messages in thread
From: Nicolas Sebrecht @ 2009-03-04 14:39 UTC (permalink / raw)
To: Tim Visher; +Cc: git
On Wed, Mar 04, 2009 at 09:01:51AM -0500, Tim Visher wrote:
> As you can see, v1.6.2 and v1.6.2-rc2 are missing from the repo that
> I'm pushing to on my thumb drive, despite it claiming it's up to date.
>
> What am I doing wrong?
You need to push the tags using the --tags option of git-push (when
pushing to your sandbox repository).
--
Nicolas Sebrecht
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Strange push/clone errors
2009-03-04 14:39 ` Nicolas Sebrecht
@ 2009-03-04 17:37 ` Tim Visher
0 siblings, 0 replies; 3+ messages in thread
From: Tim Visher @ 2009-03-04 17:37 UTC (permalink / raw)
To: Nicolas Sebrecht; +Cc: git
On Wed, Mar 4, 2009 at 9:39 AM, Nicolas Sebrecht
<nicolas.s-dev@laposte.net> wrote:
>
> On Wed, Mar 04, 2009 at 09:01:51AM -0500, Tim Visher wrote:
>
>> As you can see, v1.6.2 and v1.6.2-rc2 are missing from the repo that
>> I'm pushing to on my thumb drive, despite it claiming it's up to date.
>>
>> What am I doing wrong?
>
> You need to push the tags using the --tags option of git-push (when
> pushing to your sandbox repository).
Thank you, Nicolas! I actually discovered the `--mirror` option.
Since that's basically what I'm trying to do, that's what I ended up
going with. It appears to be working.
--
In Christ,
Timmy V.
http://burningones.com/
http://five.sentenc.es/ - Spend less time on e-mail
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-03-04 17:39 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-03-04 14:01 Strange push/clone errors Tim Visher
2009-03-04 14:39 ` Nicolas Sebrecht
2009-03-04 17:37 ` Tim Visher
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).