From: Marius Kriegerowski <marius.kriegerowski@gmail.com>
To: cgit@lists.zx2c4.com
Subject: Show 404 when switching branches when file was moved
Date: Sat, 16 Apr 2022 10:00:17 +0200 [thread overview]
Message-ID: <0874AB9A-2717-4D9A-AD51-B4B1D71952A5@gmail.com> (raw)
Hi,
This is a follow-up from this thread [REMOVED AFTER I RECEIVED A REPLY THAT THIS MESSAGE WAS BLOCKED BECAUSE OF HTML…]
When looking at a file that was moved on another branch, switching to that branch still displays that file in its original state. Example:
[REMOVED AFTER I RECEIVED A REPLY THAT THIS MESSAGE WAS BLOCKED BECAUSE OF HTML…]
Switching in the top right corner to dunfell should make clear that this file did not exist under that name on the target branch (dunfel). E.g. GitHub is showing simply a 404 which I think is reasonable.
For comparison, the same file on the GitHub clone: [REMOVED AFTER I RECEIVED A REPLY THAT THIS MESSAGE WAS BLOCKED BECAUSE OF HTML…]
The current behaviour is misleading regarding what is actually there.
Best regards
Marius
next reply other threads:[~2022-04-16 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 8:00 Marius Kriegerowski [this message]
2022-04-16 8:03 ` Marius Kriegerowski
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=0874AB9A-2717-4D9A-AD51-B4B1D71952A5@gmail.com \
--to=marius.kriegerowski@gmail.com \
--cc=cgit@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).