`ab | (cd cd git apply -)' fails with v2.0.0

2014-07-24 Thread Steffen Nurpmeso
Hello (again, psst, after a long time), it happened yesterday that i needed to do $ git diff HEAD:FILE COMMIT:SAME-FILE | (cd src git apply -) but found that didn't work with v2.0.0 (silently succeeds?, doing nothing). It works without the subshell and the cd(1); i had to use `(cd

Re: `ab | (cd cd git apply -)' fails with v2.0.0

2014-07-25 Thread Steffen Nurpmeso
Hello and good morning, Michael J Gruber g...@drmicha.warpmail.net wrote: |Junio C Hamano venit, vidit, dixit 24.07.2014 19:19: | Michael J Gruber g...@drmicha.warpmail.net writes: | Steffen Nurpmeso venit, vidit, dixit 24.07.2014 15:29: | Hello (again, psst, after a long time

--abbrev-commit gives longer hash than necessary

2016-06-30 Thread Steffen Nurpmeso
Hello, for your possible interest. For some time (currently with 2.9.0) know see that a single commit gives a longer hash than necessary, even though there is no ambiguity: ?0[steffen@wales ]$ git longca| awk 'BEGIN{l7=0;l8=0}\ /^[[:alnum:]]{7} /{++l7;next}\ /^[[:alnum:]]{8}

Re: --abbrev-commit gives longer hash than necessary

2016-07-01 Thread Steffen Nurpmeso
Hmhm. Bryan Turner wrote: You now support git too. But say, is that you with the "stay away from the storage backend if you don't have a glue!", long ago on the Mercurial list??? Ha! See how important knowledge of an aggressively garbage-collected storage backend is. I

Re: --abbrev-commit gives longer hash than necessary

2016-07-01 Thread Steffen Nurpmeso
Hello Jeff! Jeff King <p...@peff.net> wrote: |On Thu, Jun 30, 2016 at 09:38:45PM +0200, Steffen Nurpmeso wrote: |> For some time (currently with 2.9.0) know see that a single commit |> gives a longer hash than necessary, even though there is no |> ambiguity: |I don't know

v2.9.3 and v2.10.0: `name-ref' HEAD gives wrong branch name

2016-09-20 Thread Steffen Nurpmeso
Hello again, yah, sorry, i'm back again.. I try to find a way to find the name of the current branch in an automated way, because i need to ensure that a commit happens on it and no other branch. Now the problem arises that the commit ref at the time of that commit maybe shared in between

v2.10.0: ls-tree exit status is always 0, this differs from ls(1)

2016-09-21 Thread Steffen Nurpmeso
I think this behaviour contradicts the manual which strongly links ls-tree to ls(1): ?0[steffen@wales ]$ ls NEWSS ls: cannot access 'NEWSS': No such file or directory ?2[steffen@wales ]$ git ls-tree --name-only master NEWSS

Re: v2.9.3 and v2.10.0: `name-ref' HEAD gives wrong branch name

2016-09-21 Thread Steffen Nurpmeso
Hello. Jakub Narębski <jna...@gmail.com> wrote: |W dniu 20.09.2016 o 20:54, Bryan Turner pisze: |> On Tue, Sep 20, 2016 at 9:23 AM, Steffen Nurpmeso <stef...@sdaoden.eu> \ |> wrote: |>> Hello again, |>> |>> yah, sorry, i'm back again.. |>

Re: v2.10.0: ls-tree exit status is always 0, this differs from ls(1)

2016-09-21 Thread Steffen Nurpmeso
Hello. Junio C Hamano <gits...@pobox.com> wrote: |Steffen Nurpmeso <stef...@sdaoden.eu> writes: |> I think this behaviour contradicts the manual which strongly links |> ls-tree to ls(1): | |Patches to the documentation is very much welcomed. The below could serve this pur

Re: v2.10.0: ls-tree exit status is always 0, this differs from ls(1)

2016-09-21 Thread Steffen Nurpmeso
Junio C Hamano <gits...@pobox.com> wrote: |Steffen Nurpmeso <stef...@sdaoden.eu> writes: ... |Sorry, but I did not notice that there was an attached patch when I |was reading your response for the first time. Risk of using an |attachment to e-mail ;-) | |I think this issue d

Re: v2.10.0: ls-tree exit status is always 0, this differs from ls(1)

2016-09-22 Thread Steffen Nurpmeso
Hello, Michael J Gruber <g...@drmicha.warpmail.net> wrote: |Steffen Nurpmeso venit, vidit, dixit 22.09.2016 00:46: |> Junio C Hamano <gits...@pobox.com> wrote: |>|Steffen Nurpmeso <stef...@sdaoden.eu> writes: ... |>|I think this issue does not need a separate bull

Re: v2.9.3 and v2.10.0: `name-ref' HEAD gives wrong branch name

2016-09-20 Thread Steffen Nurpmeso
Hey. Bryan Turner <btur...@atlassian.com> wrote: |On Tue, Sep 20, 2016 at 9:23 AM, Steffen Nurpmeso <stef...@sdaoden.eu> \ |wrote: |> yah, sorry, i'm back again.. |> I try to find a way to find the name of the current branch in an |> automated way, because i need to

v2.15.0: commits become falsely joined when rebasing (interactively)

2017-11-18 Thread Steffen Nurpmeso
Hello again, i see an error with v2.15.0 that happened already back in early October (AlpineLinux [edge] pretty much up-to-date with newest git but please don't ask exact version). I failed to reproduce it back then, but now again, here is how. - It seems related to having a hook (pre-commit),