From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [poll] does anybody depend on RelNotes being a symbolic link?
Date: Wed, 11 Feb 2015 14:23:55 -0800 [thread overview]
Message-ID: <xmqqegpwt7d0.fsf@gitster.dls.corp.google.com> (raw)
I am wondering if I can turn the top-level RelNotes symbolic link
into a regular file.
The benefit for doing that is that I can start the file like so:
Git ???? Release Notes
======================
Updates since v2.3
early in the cycle and then later decide if we want to make the next
one 3.0 or 2.4. And then just after the release, I move it down to
Documentation/RelNotes/3.0.0.txt (or 2.4.0.txt) and start the next
cycle.
One thing that worries me is that people and their build scripts
might depend on being able to figure out the upcoming release name
by reading the symbolic link, assuming that the link would point to
Documentation/RelNotes/x.y.z.txt, and such a change ends up breaking
their setup. I am not sure how likely this would be. Objections?
Also any other objections, other possible cause of breakages I may
have missed?
reply other threads:[~2015-02-11 22:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=xmqqegpwt7d0.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.