aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* git-svn: support -C<num> passing to git-diff-treeEric Wong2006-06-16
| | | | | | The repo-config key is 'svn.copysimilarity' Signed-off-by: Eric Wong <normalperson@yhbt.net>
* git-svn: don't allow commit if svn tree is not currentEric Wong2006-06-16
| | | | | | | | | If new revisions are fetched, that implies we haven't merged, acked, or nacked them yet, and attempting to write the tree we're committing means we'd silently clobber the newly fetched changes. Signed-off-by: Eric Wong <normalperson@yhbt.net>
* git-svn: restore original LC_ALL setting (or unset) for commitEric Wong2006-06-16
| | | | | | | | | | svn forces UTF-8 for commit messages, and with LC_ALL set to 'C' it is unable to determine encoding of the git commit message. Now we'll just assume the user has set LC_* correctly for the commit message they're using. Signed-off-by: Eric Wong <normalperson@yhbt.net>
* git-svn: eol_cp corner-case fixesEric Wong2006-06-16
| | | | | | | | | | | | | | | | If we read the maximum size of our buffer into $buf, and the last character is '\015', there's a chance that the character is '\012', which means our regex won't work correctly. At the worst case, this could introduce an extra newline into the code. We'll now read an extra character if we see '\015' is the last character in $buf. We also forgot to recalculate the length of $buf after doing the newline substitution, causing some files to appeare truncated. We'll do that now and force byte semantics in length() for good measure. Signed-off-by: Eric Wong <normalperson@yhbt.net>
* git-svn: fix handling of filenames with embedded '@'Eric Wong2006-06-16
| | | | | | | | | | | | | | | | | | | | | | | svn has trouble parsing files with embedded '@' characters. For example, svn propget svn:keywords foo@bar.c svn: Syntax error parsing revision 'bar.c' I asked about this on #svn and the workaround suggested was to append an explicit revision specifier: svn propget svn:keywords foo@bar.c@BASE This patch appends '@BASE' to the filename in all calls to 'svn propget'. Patch originally by Seth Falcon <sethfalcon@gmail.com> Seth: signoff? [ew: Made to work with older svn that don't support peg revisions] Signed-off-by: Eric Wong <normalperson@yhbt.net>
* git-svn: t0000: add -f flag to checkoutEric Wong2006-06-16
| | | | | | | Some changes to the latest git.git made this test croak. So we'll always just force everything when using a new branch. Signed-off-by: Eric Wong <normalperson@yhbt.net>
* GIT 1.4.0v1.4.0Junio C Hamano2006-06-10
| | | | Signed-off-by: Junio C Hamano <junkio@cox.net>
* Merge git://git.kernel.org/pub/scm/git/gitwebJunio C Hamano2006-06-10
|\
| * v267Kay Sievers2006-05-30
| |
| * prepend '--' to filelist when calling git-diff-treeRocco Rutte2006-05-30
| |
| * v266Kay Sievers2006-05-22
| |
| * remove Christian's email addressKay Sievers2006-05-22
| |
| * v265Kay Sievers2006-05-01
| |
| * handle utf8 characters from /etc/passwdKay Sievers2006-05-01
| |
| * v264Kay Sievers2006-01-17
| |
| * fix: Use of uninitialized valueKay Sievers2006-01-17
| | | | | | | | | | | | The subroutine did not check the case where HEAD does not verify. Patch from Junio C Hamano <junkio@cox.net>
| * v263Kay Sievers2006-01-09
| |
| * allow working in repositories with textual symref HEADJunio C Hamano2006-01-09
| |
| * resolve textual hashes when looking up "refs"Kay Sievers2005-12-22
| | | | | | | | | | | | Thanks to Jon Nelson for the patch. Signed-off-by: Kay Sievers <kay.sievers@suse.de>
| * v262Kay Sievers2005-12-19
| |
| * define default colorsKay Sievers2005-12-19
| | | | | | | | | | | | Thanks to Kir Kolyshkin for pointing it out. Signed-off-by: Kay Sievers <kay.sievers@suse.de>
| * v261Kay Sievers2005-12-07
| |
| * fix leading whitespace in commit textKay Sievers2005-12-07
| | | | | | | | Signed-off-by: Kay Sievers <kay.sievers@suse.de>
| * more tagsKay Sievers2005-12-07
| | | | | | | | Signed-off-by: Kay Sievers <kay.sievers@suse.de>
| * v260Kay Sievers2005-12-07
| |
| * attach tag to the linkKay Sievers2005-12-07
| | | | | | | | Signed-off-by: Kay Sievers <kay.sievers@suse.de>
| * v259Kay Sievers2005-12-07
| |
| * show multiple tagsKay Sievers2005-12-07
| | | | | | | | Signed-off-by: Kay Sievers <kay.sievers@suse.de>
| * v258Kay Sievers2005-12-07
| |
| * show tags in listsKay Sievers2005-12-07
| | | | | | | | Signed-off-by: Kay Sievers <kay.sievers@suse.de>
| * v257Kay Sievers2005-11-24
| |
| * fix "rename" outputKay Sievers2005-11-24
| | | | | | | | Signed-off-by: Kay Sievers <kay.sievers@suse.de>
| * v256Kay Sievers2005-11-24
| |
| * fix quoted filename lookupKay Sievers2005-11-24
| | | | | | | | Signed-off-by: Kay Sievers <kay.sievers@suse.de>
| * v255Kay Sievers2005-11-24
| |
| * v254Kay Sievers2005-11-24
| |
| * allow utf8 characters in url parameter escapeKay Sievers2005-11-24
| | | | | | | | Signed-off-by: Kay Sievers <kay.sievers@suse.de>
| * v253Kay Sievers2005-11-23
| |
| * set logo output to raw modeKay Sievers2005-11-23
| |
| * add broken latin encoding to test fileKay Sievers2005-11-23
| |
| * add ut8 test fileKay Sievers2005-11-23
| | | | | | | | It contains Märchen. (\xc3a4)
| * fix utf8 decodingKay Sievers2005-11-23
| | | | | | | | Signed-off-by: Kay Sievers <kay.sievers@suse.de>
| * v252Kay Sievers2005-11-20
| |
| * fix another typoKay Sievers2005-11-20
| | | | | | | | Signed-off-by: Kay Sievers <kay.sievers@suse.de>
| * v251Kay Sievers2005-11-20
| |
| * add missing esc() renameKay Sievers2005-11-20
| | | | | | | | Signed-off-by: Kay Sievers <kay.sievers@suse.de>
| * v250Kay Sievers2005-11-19
| |
| * replace invalid utf8 sequences by UTF-8 REPLACEMENT CHARACTER (efbfbd)Kay Sievers2005-11-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I still strongly disagree with the git maintainers not to hint people, to use the only sane default encoding for a distributed project, which is utf8. I'm tired of hearing filesystem development arguments. Git is a software offered to merge forth and back across the world and not to provide a content neutral filesystem. Btw: I have nothing against the ability to run git in a closed environment, with a different encoding, that's fine, sure. But that is obviously not the case for the projects on kernel.org. It's about sane defaults, nothing else. You have to make decisions guy, as always in life. The problems to allow random encoded garbage in commit messages _without_ storing the encoding, just makes zero sense. Eighter you introduce a per-commit encoding field, if you insist on this craziness, or you define a default encoding. Everything else is just lazy and does not solve any problem, besides that you can claim now, that you are not responsible for the mess in the repository. Gitweb shows several commits at once, you allow various encodings committed to the same repository, without any hint what that garbage from the individual commits is encoded with. No idea why you don't get the problem - it's unsolvable. If you merge different peoples work, you have to speak a common language! Kay Sievers <kay.sievers@vrfy.org>
| * escape ' ' with '+' in url'sKay Sievers2005-11-14
| |
| * v249Kay Sievers2005-11-14
| |
generated by cgit v1.2.1 (git 2.18.0) at 2025-01-08 13:20:31 +0000