mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <>
To: "tionis" <>
Cc: <>
Subject: Re: bug report: git push fails in worktree
Date: Tue, 06 Dec 2022 10:42:47 +0900	[thread overview]
Message-ID: <xmqqr0xdnw88.fsf@gitster.g> (raw)
In-Reply-To: <COUBW3AG192J.1UCDLVUZ38VJA@tempest> (tionis's message of "Tue, 06 Dec 2022 02:03:14 +0100")

"tionis" <> writes:

> Thank you for filling out a Git bug report!
> Please answer the following questions to help us understand your issue.
> What did you do before the bug happened? (Steps to reproduce your issue)
> Setup two branches.  
> Check the main one out in a repo.  
> Checkout the second one using a worktree with
> ...
> Execute git push

There must be some steps missing still in the above description.
You seem to be expecting "git push" to push things out to
somewhere, but in the above sequence (I am assuming that you started
with "git init" to create a local repository), there is nothing I
see that tells "git push" where to push to.  There must have been
some step not described above that sets configuration to tell where
to push what when "git push" is run without "where to" and "what"
on the command line.

Well, I am assuming too much.  Your "Execute git push" may not mean
"type g i t SPACE p u s h RETURN and do nothing else" (it may mean
"run 'git push <RETURN>'", for
example, and readers cannot tell).

If you didn't use an extra worktree, but otherwise do the same
thing, does "git" push out what you expect it to?

  reply	other threads:[~2022-12-06  1:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06  1:03 bug report: git push fails in worktree tionis
2022-12-06  1:42 ` Junio C Hamano [this message]
2022-12-06 11:23   ` tionis

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqr0xdnw88.fsf@gitster.g \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).