Feature request : "git fsck" should show the percentage of completeness in step "Checking connectivity:"

as "git fsck" does it already for "Checking objects:" Is this a valid feature request? -- Toralf PGP C4EACDDE 0076E94E

gitk takes a looong time for a subdir of the Gentoo repository

steps to reproduce: $> git clone git://git.gentoo.org/repo/gentoo.git $> cd gentoo $> gitk sys-apps/portage-mgorny For few minutes I do just read here : "Reading commits..." -- Toralf PGP C4EACDDE 0076E94E signature.asc Description: OpenPGP digital signature

Re: enhancement request : If 2 commits to be squashed together do have the same title and comment ...

On 07/09/2017 08:52 PM, Junio C Hamano wrote: > In the form, it is valid---sending a message to git@vger.kernel.org > is the right way to describe a problem and ask for a help (or better > yet, propose a solution ;-). > > I am guessing that you are talking about "squash" in "rebase -i" > command?

enhancement request : If 2 commits to be squashed together do have the same title and comment ...

... then jast squsash them w/o questioning. Is this a valid RFE ? -- Toralf PGP C4EACDDE 0076E94E

Re: [boinc_dev] (local ?) BOINC repo broken again -or- how to act on the CR/LF changes made upstream

On 09/14/2014 10:51 AM, Torsten Bögershausen wrote: It may be that there is a bug in the tools you are using. I use git 2.1.0 -- Toralf pgp key: 0076 E94E -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info

Re: [boinc_dev] (local ?) BOINC repo broken again -or- how to act on the CR/LF changes made upstream

On 09/12/2014 09:10 PM, Rom Walton wrote: I found this: http://stackoverflow.com/questions/17223527/how-do-i-force-git-to-checkout-the-master-branch-and-remove-carriage-returns-aft That might help in the future. This helped : git reset --hard 9e860d0451 git pull git clean -f git gc git

(local ?) BOINC repo broken again -or- how to act on the CR/LF changes made upstream

-Web.po locale/zh_TW/BOINC-Web.po Please, commit your changes or stash them before you can merge. Aborting Attached are my ~/.gitconfig and ~/devel/boinc-v2/.git/config -- Toralf pgp key: 0076 E94E [user] email = toralf.foers...@gmx.de name = Toralf Förster

Re: [boinc_dev] (local ?) BOINC repo broken again -or- how to act on the CR/LF changes made upstream

On 09/12/2014 08:19 PM, Rom Walton wrote: Try: git checkout -f master git pull origin I committed fixes for that stuff this morning. doesn't helped : tfoerste@n22 ~/devel/boinc-v2 $ git checkout -f master Already on 'master' Your branch is behind 'origin/master' by 7 commits, and can be

Re: [boinc_dev] (local ?) BOINC repo broken again -or- how to act on the CR/LF changes made upstream

On 09/12/2014 08:55 PM, Rom Walton wrote: Crud... Well, personally, I would delete the locale directory and the two translation files in html. Do the 'git pull', and then switch between master and some other branch. like: git checkout -f client_release/7/7.4 git checkout -f master

sort entries numerically

Hi, is there any chance to have 1.8 before 1.10 in an output like the following : ... From https://code.wireshark.org/review/wireshark 52fe0aa..b69642d master - origin/master 460db8a..540f061 master-1.10 - origin/master-1.10 25bb29a..5741a40 master-1.12 - origin/master-1.12

git pull does no longer work due to a Cr-Lf issue

: Your local changes to the following files would be overwritten by merge: lib/boinc_win.h Please, commit your changes or stash them before you can merge. Aborting /me wonders how to solve this w/o cloning the complete repo again. - -- MfG/Sincerely Toralf Förster pgp finger print:1A37

(broken ?) output of git diff --color-word

]]; then # SHARES=/tmp# SHARES=$SHARES /mnt/hostfs# SHARES=$SHARES /mnt/nfsv2# SHARES=$SHARES /mnt/nfsv3 # SHARES=$SHARES /mnt/nfsv4 echo $SHARES | grep -q hostfs -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3

why doesn't git bisect visualize show all commit ids from the bisect log

When run that command immediate after git bisect start somebody sees the full commit range as defined in git bisect start. However running that command later after few git bisect steps somebody is just presented with the remaining commit interval. Is this intended ? -- MfG/Sincerely Toralf

Re: why doesn't git bisect visualize show all commit ids from the bisect log

On 09/20/2013 08:22 PM, Jonathan Nieder wrote: Hi Toralf, Toralf Förster wrote: When run that command immediate after git bisect start somebody sees the full commit range as defined in git bisect start. However running that command later after few git bisect steps somebody is just

Re: RFC: git bisect should accept paths-to-be-excluded

On 09/17/2013 09:26 AM, Christian Couder wrote: Hi, On Mon, Sep 16, 2013 at 2:39 PM, Toralf Förster toralf.foers...@gmx.de wrote: I'm bisecting a linux kernel issue and want to ignore all commits just touching something in ./drives/staging. Currently the only way would be to specify all

RFC: git bisect should accept paths-to-be-excluded

I'm bisecting a linux kernel issue and want to ignore all commits just touching something in ./drives/staging. Currently the only way would be to specify all dir/subdir combination under ./linux except that particular directory, right ? -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A

gitk doesn't always shows boths tags in gitk tag1..tag2

client_release_7.0.44 : $ gitk client_release_7.0.44..client_release_7.0.45 Now I'm wondering whether this is a side effect of the developer model of BOINC or an issue in gitk ? -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 -- To unsubscribe

Re: gitk doesn't always shows boths tags in gitk tag1..tag2

client_release_7.0.44..client_release_7.0.45 shows 468 rows. Thx for the quick answer :-) -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord

Re: problem with BOINC repository and CR/LF

is stat-dirty. /me still wonders whether this race condition is a feature or an issue in GIT - b/c it means that 2 different people cloning the same repository get different results. -Peff -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3

Re: RFC: git config -l should not expose sensitive information

think that attempting to do this would only result in a false sense of security. -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord

Re: problem with BOINC repository and CR/LF

On 12/18/2012 01:15 PM, Torsten Bögershausen wrote: HTH /Torsten Thx Torsten - I forwarded this answer (and all the other answers) to the boinc alpha mailing list - there's now a discussion about that. -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508

Re: problem with BOINC repository and CR/LF

is stat-dirty. Ah - /me was wondering why sometimes (but rarely) I could not exactly reproduce the problem and was really wondering if the underlying file system (ext4) would give an extra layer of trouble or not. Thx for that explanation. -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A

Re: problem with BOINC repository and CR/LF

On 12/18/2012 10:55 AM, Toralf Förster wrote: failed test(s): t3600 t7508 fixed 0 success 8342 failed 8 broken 56 total 8528 ick forgot these : n22 /usr/portage/dev-vcs/git # grep -i ^not ok /tmp/git.log | grep -v TODO not ok - 15 Test that git rm -f fails if its rm fails not ok

Re: problem with BOINC repository and CR/LF

On 12/18/2012 02:56 AM, Andrew Ardill wrote: On 18 December 2012 03:01, Toralf Förster toralf.foers...@gmx.de wrote: On 12/17/2012 12:38 PM, Andrew Ardill wrote: On 17 December 2012 21:23, Toralf Förster toralf.foers...@gmx.de wrote: Hello, I'm faced with this situation : http

problem with BOINC repository and CR/LF

a problem. FWIW I already played (unsuccessful) with this too: $ grep -B 3 crlf .gitconfig confirm = never [core] autocrlf = true -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 -- To unsubscribe from this list: send the line

RFC: git config -l should not expose sensitive information

often the output is requested in help forums - and a git config -l | wgetpaste exposes parameters like sendmail.smtppass - so hide those variables in the output (if not explicitly wanted) would makes sense, or ? -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A

Re: problem with BOINC repository and CR/LF

On 12/17/2012 12:38 PM, Andrew Ardill wrote: On 17 December 2012 21:23, Toralf Förster toralf.foers...@gmx.de wrote: Hello, I'm faced with this situation : http://lists.ssl.berkeley.edu/mailman/private/boinc_alpha/2012-December/017371.html and even a git stash doesn't help. Hi Toralf