From: "Stephen Cuppett" <cuppett@gmail.com>
To: git@vger.kernel.org
Subject: [RFC] Change handling of RelNotes
Date: Thu, 30 Aug 2007 21:35:36 -0400 [thread overview]
Message-ID: <316a20a40708301835hc4236d4tdb289b6f705ab86@mail.gmail.com> (raw)
I went to clone git onto a memory stick today. The default fs on the
sticks doesn't support symlinks. After looking a little bit, the only
symlink I can see in the source tree is RelNotes. It appears when
going to a new release the file gets created in /Documentation and the
symlink updated.
I propose we eliminate this symlink. There are multiple other things
we can do to eliminate it and make the repository more flexible across
filesystems:
* Always have current release in /Documentation/RelNotes and keep the
prior versions named the way they are maintained now. When starting a
new release, rename the file and create it again.
* Keep the current in RelNotes and leave the archived ones in
/Documentation. Doing same content move and clear operation when
starting a new release.
* Keep two copies RelNotes and /Documentation/RelNotes-X.X.X that
essentially have same content and RelNotes has a lot of churn
* others...?
With this one abnormality the git repo on a normal flash drive doesn't
work... at least in my case.
next reply other threads:[~2007-08-31 1:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 1:35 Stephen Cuppett [this message]
2007-08-31 1:39 ` [RFC] Change handling of RelNotes Petr Baudis
2007-08-31 6:04 ` Junio C Hamano
2007-08-31 2:21 ` Junio C Hamano
2007-08-31 6:08 ` Marius Storm-Olsen
2007-08-31 6:44 ` Nanako Shiraishi
2007-08-31 7:09 ` Junio C Hamano
2007-08-31 7:22 ` [PATCH] autodetect core.symlinks in git-init Junio C Hamano
2007-08-31 8:00 ` Nanako Shiraishi
2007-08-31 8:23 ` Marius Storm-Olsen
[not found] ` <316a20a40708310539w1d20c391w8566a042c7a8679a@mail.gmail.com>
2007-08-31 12:52 ` [RFC] Change handling of RelNotes Stephen Cuppett
2007-08-31 20:25 ` Junio C Hamano
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=316a20a40708301835hc4236d4tdb289b6f705ab86@mail.gmail.com \
--to=cuppett@gmail.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 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).