From: "Kristoffer Haugsbakk" <code@khaugsbakk.name>
To: "Gabor Urban" <urbangabo@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Question about migrating a repository
Date: Fri, 16 Feb 2024 20:46:11 +0100 [thread overview]
Message-ID: <6965c59e-8edd-4d91-81da-3600a61569a3@app.fastmail.com> (raw)
In-Reply-To: <CAL=1hhwreG_W_Ch-B5DXioqjUsfkgjayNZbkCk7uOv3vc=TBSQ@mail.gmail.com>
On Fri, Feb 16, 2024, at 20:34, Gabor Urban wrote:
> Hi guys,
>
> I need a bit help.
>
> I have migrated my git repository from my old computer using a bundle.
> (The repo was local with no clones.) That computer will be dismantled
> and thrown away.
>
> I checked and verything is working fine till I get a git status
> report. The most relevant part is:
>
> On branch master
> Your branch is up to date with 'origin/master'.
>
> I would like to make THIS repository to be the "origin". (The other
> will be destroyed.) How could I do that?
>
> Thanks for any help in advance,
`origin/master` is a “remote-tracking branch”. It points to `master` on
the `origin` remote. Or to be precise: it points to a ref that you use
to track this branch from that remote. A remote is some other repository
that you have a link to, like a URL.
That ref (reference) was updated with a command like `git fetch`.
You can get the link to that remote with
```
git remote get-url origin
```
Your own local repository is never a remote like `origin`. You don’t
have to make your own repository into a remote.
Your repository is fine. There’s nothing that you need to do.
>
>
> --
> Urbán Gábor
>
> Linux is like a wigwam: no Gates, no Windows and an Apache inside.
--
Kristoffer Haugsbakk
next prev parent reply other threads:[~2024-02-16 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 19:34 Question about migrating a repository Gabor Urban
2024-02-16 19:46 ` Kristoffer Haugsbakk [this message]
2024-02-17 1:22 ` Chris Torek
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=6965c59e-8edd-4d91-81da-3600a61569a3@app.fastmail.com \
--to=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=urbangabo@gmail.com \
/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