From: petr.vorel at gmail.com (Petr Vorel)
Subject: [PATCH v2] ui-shared: split repository link into directories
Date: Fri, 29 Apr 2016 07:05:11 +0200 [thread overview]
Message-ID: <20160429050510.GA979@x230> (raw)
In-Reply-To: <20160428231435.GB27214@x230>
Dear John,
> > We may just have to bail out of this feature if the two variables differ.
> Is it really the best way from UI/UX POV? Inconsistency isn't nice :-(. I'd like to try
> to have this feature either on or off for each repository.
You were right, it doesn't make much sense to split links if the paths (repo.url and
repo.name) are different (even if number of levels is the same for both of them).
I'll skip it in v3.
I'll wrap the feature in option which default off.
Kind regards,
Petr
prev parent reply other threads:[~2016-04-29 5:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 21:24 petr.vorel
2016-04-28 23:14 ` petr.vorel
2016-04-29 5:05 ` petr.vorel [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=20160429050510.GA979@x230 \
--to=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).