Here are the leftover pieces I have in todo:TODO file that I did
not mention in the earlier messages. I left them out from the
third message of this series, as (1) some are more of "trivial
fix" category, and (2) others are heavier and would probably not
fit for a single release cycle such as 1.5.3.
The easier ones
---------------
* parse-remote.sh has POSIXLY incorrect shell construct.
Message-ID: <20070505080313.GA12170@xxxxxxxxxxxxxxxxxxx>
* Use 'git diff' not 'git diff-tree' in merge and rebase
From: James Bowes <jbowes@xxxxxxxxxxxxxxxxxx>
Message-ID: <1178398134288-git-send-email-jbowes@xxxxxxxxxxxxxxxxxx>
* gitk --left-right
From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Message-ID: <alpine.LFD.0.98.0705051524300.17381@xxxxxxxxxxxxxxxxxxxxxxxxxx>
From: Junio C Hamano <junkio@xxxxxxx>
Message-ID: <7vabwifl23.fsf@xxxxxxxxxxxxxxxxxxxxxxxx>
* Handling pushing into non-bare repository more gracefully.
When git-push is done to a non-bare repository and updates the
branch that is currently checked out, we currently do not do
anything special.
From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Message-ID: <Pine.LNX.4.64.0704160931550.5473@xxxxxxxxxxxxxxxxxxxxxxxxxx>
* git-daemon bug?
From: Franck Bui-Huu <vagabon.xyz@xxxxxxxxx>
Message-ID: <450EABD0.1040102@xxxxxxxxxxxxxxx>
Repeated requests against git-daemon makes it stuck under --syslog
[jc: does not reproduce easily for me; has anybody seen it?]
* AsciiDoc 8 would break our documentation.
From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
Message-ID: <4523EC14.6070806@xxxxxxxxxxxxxxxxx>
AsciiDoc 8 does not grok documents written for AsciiDoc 7 out of
the box.
[jc: limbo?]
* Delegate gitweb part to somebody else.
* Use gitattributes for more things.
- 'precious' files that are not tracked but not
build-products. Currently people seem to put them in
.gitignore, but that is not quite right, as .gitignore is
meant for ignoring things that can be lost (build products,
editor backup files). "git clean -x" and "git checkout" to
another branch that has a file where the current branch has a
directory could lose such 'precious' files.
- Customized "diff -p" markers per path (Johannes, on #git
2007-04-30).
I think it makes sense to give an extra parameter to xdiff
machinery to affect how "diff -p" markers are constructed (as
opposed to teach xdiff machinery to read gitattributes -- the
code does not have path information at that level). The
simplest interface would be to pass a regexp and have the
existing code always look for that regexp backwards. A more
complex one would involve a callback function, but I do not
know if that kind of complexity is worth it.
- Others???
* upload-pack support for start fetching from any valid point on
the history, not just published refs. (Erik W. Biederman
<m164jc9ekx.fsf@xxxxxxxxxxxxxxxxxxxxxxxxx>)
* Give --stdin to git-log, similar to git-rev-list
From: "Marco Costalba" <mcostalba@xxxxxxxxx>
Message-ID: <e5bfff550705110413q28aef3d8k3aeb0d342eeb2016@xxxxxxxxxxxxxx>
* Update the lockfile protocol so that closing and renaming are
done inside lockfile commit time. Some filesystems do not
like an open file renamed and then closed. Come up with a
patch and pass Alex for an Ack.
Probably not so important ones
------------------------------
* daemon --strict-symlink.
* Maybe grok PGP signed text/plain in applymbox as well.
* Mbx (not mbox) support for git-mailsplit.
* git-proxy should be spawned with sh -c 'command' $1 $2.
[jc: should it? -- deciding if it should may not be "trivial",
but if it turns out to be the right thing to do, the change
itself is trivial.]
* Maybe a true git-proxy command that reads the first request
pkt-line, and redirects the request to its real destination.
* test scripts for the relative directory path stuff.
The heavier ones
----------------
* Use blame machinery to track a single file (not path) in a finer
grained way.
From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Message-ID: <alpine.LFD.0.98.0704201554550.9964@xxxxxxxxxxxxxxxxxxxxxxxxxx>
[jc: I have a fixed-up one parked in 'pu' and also outlined what
other things I think are needed in my response:
Message-ID: <7vwt06wqv8.fsf@xxxxxxxxxxxxxxxxxxxxxxxx>
]
* "git fetch" should be able to use foreign SCM import backends
such as svnimport and cvsimport.
* git-clone fails .git/refs/foo (Yann Dirson <ydirson@xxxxxxxxxx>)
<20060610225040.GA7766@xxxxxxxxxxxxx>
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
