From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Cc: Linus Torvalds <torvalds@osdl.org>
Subject: Current status toward 0.99.5 and beyond
Date: Tue, 23 Aug 2005 10:14:47 -0700 [thread overview]
Message-ID: <7vmzn8poc8.fsf@assigned-by-dhcp.cox.net> (raw)
Some people may have noticed that the progress of the master
branch head has somewhat slowed down lately, and I have kept
some changes in the proposed updates branch for quite some time.
There are two reasons for this. One is that I've been quite
busy during my day job hours, and haven't had enough time to
make sure the multi-head fetch stuff does not break things and
the way it works is reasonable. Another is that I am feeling
guilty about letting Documentation go stale, and am reluctant to
have what is in the proposed updates branch graduate to the
master branch without accompanying documentation. Maybe I'll
have some time on my next GIT day [*1*].
Anyway, here is my updated Itchlist, as a preview of what comes
next.
For 0.99.5, I would like to finish testing and documenting what
is currently in the proposed updates branch. There are two
changes there: multi-head fetch and $GIT_DIR/remotes/ that
somewhat deprecates $GIT_DIR/branches/; semantics cleanup of
"git reset" command.
Linus has been feeding updates to make various commands to be
capable of running from subdirectories and taking paths relative
to the current directory. I would have liked these patches with
test scripts to demonstrate they do what they claim to do well.
Patches to extend existing test scripts in t/ directory are very
much welcomed. So far, the following commands should be usable
with relative directory paths:
update-cache
ls-files
diff-files
diff-cache
diff-tree
I do not have major itch after 0.99.5 right now, except for
obvious fixes and tweaks here and there [*2*]. I think we would
concentrate a bit more on usability enhancement including the
tutorial updates. One code change I would like to see is to add
limited MIME support to applymbox suite. We should be able to
teach mailinfo to:
- detect B encoding in the mail headers, and translate it to UTF-8;
- understand a single level multipart and pick out the body of
the message;
- detect QP in the body and decode into the original charset;
- after splitting the body into commit log and patch, translate only
the commit log part into UTF-8.
[Footnote]
*1* Currently, my Wednesdays and Saturdays are for GIT only.
*2* Here is a list of minor itches:
* "git rebase" could be a bit more tolerant to conflicting
patches. We may want to "wiggle" it, or may want to run
3-way "merge".
* The semantics of rev-parse needs to be clarified.
* show-branch may want to show things in topological order, not
time-based order.
* There are commands that were well intentioned but not useful
in practice, like build-rev-cache. I would like to review
them for removal.
* Cloning a packed repository over HTTP should work natively
now. Update "git clone" and remove "git-clone-dumb-http".
next reply other threads:[~2005-08-23 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 17:14 Junio C Hamano [this message]
2005-08-23 17:31 ` Current status toward 0.99.5 and beyond Linus Torvalds
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=7vmzn8poc8.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).