From: "SZEDER Gábor" <szeder.dev@gmail•com>
To: Taylor Blau <me@ttaylorr•com>
Cc: Jude Guan Wang <guan@clicktherapeutics•com>, git@vger•kernel.org
Subject: Re: Fwd: Issue with Git Branch
Date: Mon, 13 Jan 2020 12:26:21 +0100 [thread overview]
Message-ID: <20200113112621.GJ32750@szeder.dev> (raw)
In-Reply-To: <20200113004814.GA15236@syl.local>
On Sun, Jan 12, 2020 at 04:48:14PM -0800, Taylor Blau wrote:
> On Mon, Jan 13, 2020 at 01:42:35AM +0100, SZEDER Gábor wrote:
> > On Sun, Jan 12, 2020 at 04:11:43PM -0800, Taylor Blau wrote:
> > > On Sun, Jan 12, 2020 at 07:01:04PM -0500, Jude Guan Wang wrote:
> > > > I noticed something weird with my git command. In my local
> > > > environment I seem to have a branch named `-D`:
> > > >
> > > > And I don’t remember how I was able to create a branch like that.
> >
> > > If you do find a reproducible way to create branches named '-D' or
> > > similar, please do let us know, as these are not intended to be valid
> > > branch names in general.
> >
> > $ git update-ref refs/heads/-D master
> > $ git branch |head -n1
> > -D
>
> I was assuming that Jude had gotten the ref to appear by using 'git
> branch' alone, i.e., without the help of 'git update-ref' or 'cp
> .git/refs/heads/{master,-D}'.
On a somewhat related note, while trying whether I could
"inadvertently" create such a branch with gitk I stumbled upon this
bit of weirdness:
$ git rev-parse v2.24.0^{commit}
da72936f544fec5a335e66432610e4cef4430991
$ git branch da72936f544fec5a335e66432610e4cef4430991 v2.24.0
$ gitk -1 v2.24.0
(While starting up gitk might show a popup warning about the branch
with 40 hexdigit name, close it.)
So now gitk displays a commit with the v2.24.0 tag and the da7293...
branch pointing to it. Right click on the commit's subject line,
select "Create new branch" from the context menu. Enter "-D" as the
name of the new branch, and click Create. Now gitk displays a "-D"
branch pointing to the same commit as well, but it's only a display
thing, as it did not actually create that branch, because it
carelessly run the 'git branch -D da7293...' command... After
refreshing with F5 it won't display the da7293... and "-D" branches.
prev parent reply other threads:[~2020-01-13 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56F9DC91-740F-47C7-9C2A-B6B1EC3A12B6@clicktherapeutics.com>
2020-01-13 0:01 ` Fwd: Issue with Git Branch Jude Guan Wang
2020-01-13 0:11 ` Taylor Blau
2020-01-13 0:42 ` SZEDER Gábor
2020-01-13 0:48 ` Taylor Blau
2020-01-13 11:26 ` SZEDER Gábor [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=20200113112621.GJ32750@szeder.dev \
--to=szeder.dev@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=guan@clicktherapeutics$(echo .)com \
--cc=me@ttaylorr$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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