Re: Rewrite cat-file.c : need help to find a bug

p = 0x55a66c30, disk_sizep = 0x0, delta_base_sha1 = 0x0, typename = 0x0, contentp = 0x0, whence = OI_LOOSE, u = {packed = {pack = 0x0, offset = 0, is_delta = 0}}} Ok we can see that "disk_sizep = 0x0" which means that it segfault because line 1496 tries to read the value pointed to by disk_sizep which is NULL. I hope this will help you. Best, Christian.

Re: Rewrite cat-file.c : need help to find a bug

2017-12-29 17:04 GMT+03:00 Оля Тележная : > 2017-12-29 16:22 GMT+03:00 Jeff King : >> On Fri, Dec 29, 2017 at 01:05:50PM +0300, Оля Тележная wrote: >> >>> Hi everyone, >>> I am trying to reuse formatting logic from ref-filter in cat-file >>> command. Now

Re: Rewrite cat-file.c : need help to find a bug

2017-12-29 16:22 GMT+03:00 Jeff King : > On Fri, Dec 29, 2017 at 01:05:50PM +0300, Оля Тележная wrote: > >> Hi everyone, >> I am trying to reuse formatting logic from ref-filter in cat-file >> command. Now cat-file uses its own formatting code. >> I am trying to achieve that

Re: Rewrite cat-file.c : need help to find a bug

On Fri, Dec 29, 2017 at 01:05:50PM +0300, Оля Тележная wrote: > Hi everyone, > I am trying to reuse formatting logic from ref-filter in cat-file > command. Now cat-file uses its own formatting code. > I am trying to achieve that step-by-step, now I want to invoke > populate_value function, and I

Rewrite cat-file.c : need help to find a bug

work will go further, but now I need to fix current situation. You could write here or leave comments in github if you have any ideas. Thank you in advance for your help! Olga

PLEASE I NEED YOUR HELP FOR SCHOOL!

to leave my situation here to come over to your country to continue my education. I have made research before contacting you and please I want you to help me come to your country to start my new life. I will tell you more about my condition if you are willing to help me come over to your country

Re: Need help migrating workflow from svn to git.

Hi Josef, On 20/12/2017 12:43, Josef Wolf wrote: > >> $ git add -u >> $ git reset > > This would be added after the "git checkout -m -B master FETCH_HEAD" > command? Yes, so it would be something like this: git fetch origin master && #1 git checkout -m -B master

Re: Need help migrating workflow from svn to git.

On Wed, Dec 20, 2017 at 12:43:37PM +0100, Josef Wolf wrote: > Thanks to you both for your patience with me. Sorry for the late reply, my day > job was needing me ;-) > > On Fri, Dec 15, 2017 at 07:58:14PM +0100, Igor Djordjevic wrote: > > On 15/12/2017 17:33, Junio C Hamano wrote: > > > > > >

Re: Need help migrating workflow from svn to git.

On Fri, Dec 15, 2017 at 11:09:17AM -0800, Junio C Hamano wrote: > Igor Djordjevic writes: > > > Junio, what about consecutive runs, while merge conflicts are still > > unresolved? > > The impression I got was that the original running with svn does not > deal with

Re: Need help migrating workflow from svn to git.

Thanks to you both for your patience with me. Sorry for the late reply, my day job was needing me ;-) On Fri, Dec 15, 2017 at 07:58:14PM +0100, Igor Djordjevic wrote: > On 15/12/2017 17:33, Junio C Hamano wrote: > > > > $ git fetch > > $ git checkout -m -B FETCH_HEAD For some reason,

Re: Need help migrating workflow from svn to git.

On 15/12/2017 20:09, Junio C Hamano wrote: > > > Junio, what about consecutive runs, while merge conflicts are still > > unresolved? > > The impression I got was that the original running with svn does not > deal with conflicting situation anyway, so I did not think about it > at all, and I

Re: Need help migrating workflow from svn to git.

Igor Djordjevic writes: > Junio, what about consecutive runs, while merge conflicts are still > unresolved? The impression I got was that the original running with svn does not deal with conflicting situation anyway, so I did not think about it at all, and I

Re: Need help migrating workflow from svn to git.

On 15/12/2017 17:33, Junio C Hamano wrote: > > $ git fetch > $ git checkout -m -B FETCH_HEAD ... aaand that`s how you do it[1] without a temporary branch :) Junio, what about consecutive runs, while merge conflicts are still unresolved? Seeing Josef having a pretty relaxed flow,

Re: Need help migrating workflow from svn to git.

Hi Josef, Thank you for your patient answers. From what you said here and in that other reply[1], it looks like you know what you`re doing, you`re aware of circumstances, and you still prefer doing it that way. So, here it goes... :) On 15/12/2017 13:47, Josef Wolf wrote: > > > I`m thinking

Re: Need help migrating workflow from svn to git.

t; behavior of "svn update"? You do not mind a temporary inconsistency while "svn update" runs (it starts to update a file you may have local changes, but your test may run while the update is in the middle of it). So perhaps something along the lines of this would help. Assumin

Re: Need help migrating workflow from svn to git.

On Fri, Dec 15, 2017 at 02:17:40AM +0100, Igor Djordjevic wrote: > > This said, and without having you to change your habits too much (nor > use Git in possibly awkward ways), I`m thinking you may actually > benefit of using `git worktree add `[1] to create a > temporary working tree ("working

Re: Need help migrating workflow from svn to git.

Thanks for your input, Igor! On Thu, Dec 14, 2017 at 11:27:09PM +0100, Igor Djordjevic wrote: > Aside "update and merge" working copy while you`re hacking on it, > what happens with "execute" part? It seems really strange that you > don`t mind cron job running the same scripts which you are

Re: Need help migrating workflow from svn to git.

Thanks for your answer, Randall, On Thu, Dec 14, 2017 at 04:07:15PM -0500, Randall S. Becker wrote: > > You might want to consider a slight modification to your approach as > follows. > Instead of using git pull, use git fetch. > Have each system on its own branch (sys1 = my-sys1-branch, for

Re: Need help migrating workflow from svn to git.

On 14/12/2017 23:27, Igor Djordjevic wrote: > > As you basically have a flow where two users (you and cron job) can > edit same files at the same time, desired outcome might be a bit > ambiguous, especially when scheduled execution of those files is > added to the mix. This said, and without

Re: Need help migrating workflow from svn to git.

Hi Josef, I`m not a Git expert, and I know less of Subversion, but following your explanation, I might try to help, at least until more experienced people join. On 14/12/2017 14:09, Josef Wolf wrote: > > Every machine has a working copy of the repository in a specific > directory. A

RE: Need help migrating workflow from svn to git.

> On December 14, 2017 8:10 AM, Josef Wolf wrote: > Subject: Need help migrating workflow from svn to git. > > Hello folks, > > I am wondering whether/how my mode of work for a specific project > (currently based on SVN) could be transferred to git. > > I have a

Need help migrating workflow from svn to git.

Hello folks, I am wondering whether/how my mode of work for a specific project (currently based on SVN) could be transferred to git. I have a repository for maintaining configuration of hosts. This repository contains several hundered scripts. Most of those scripts are don't depend on each

missing entries in "git help repository-layout"

while writing up a cheat sheet with a visual layout of .git for my students, i compared "git help repository-layout" to my git clone of the kernel source tree, and noted the following things are not mentioned in the repo layout help page -- i have no idea how complete that page i

gitk --version and --help

Would be useful if these missing options could be added. Was just checking the version using regular git when I noticed. $ git --version git version 2.7.4 I'm not a member of the list, so please cc me in any replies. Cheers, Jonny

[PATCH v3 3/3] stash: remove now superfluos help for "stash push"

With the 'git stash save' interface, it was easily possible for users to try to add a message which would start with "-", which 'git stash save' would interpret as a command line argument, and fail. For this case we added some extra help on how to create a stash with a messag

Do you need financial help?

Do you need a loan to enhance your business?, Loan to consolidate your debt,Loan for personal use, Loan for credit Card, Medical Care loan,Car Loan,Mortgage Loan, Student Loan, loan for any purposes? e.t.c.Get loan at 1% interest rate annually, Hurry up now and fill out this below application

I NEED YOUR URGENT HELP AND CORPERATION

Dear Friend I am contacting you on a business deal of $9,500,000.00 Million United States Dollars, ready for transfer into your own personal account and if we make this claim, we will share it on the ratio of 50% / 50% basis, I would like to assure you that it be 100% risk free and it will be

Re: Help

Hi, On Thu, Sep 28, 2017 at 3:21 AM, Nityananda wrote: > Hello, > I am new to this community. I am facing a problem while using the > "make" command inside the "t/" folder. > > The error is > > > "1..31 > Makefile:49: recipe for target 't5551-http-fetch-smart.sh'

Help

ng directory '/home/nitya/projects/git/t' Makefile:36: recipe for target 'test' failed make: *** [test] Error 2" It will really be an act of kindness if you help me out. Regards, Nityananda Gohain

Re: [PATCH 3/3] parse-options: only insert newline in help text if needed

Junio C Hamano <gits...@pobox.com> writes: > Brandon Casey <draf...@gmail.com> writes: > >> Currently, when parse_options() produces a help message it always emits >> a blank line after the usage text to separate it from the options text. >> If the opti

Re: [PATCH 3/3] parse-options: only insert newline in help text if needed

Brandon Casey <draf...@gmail.com> writes: > Currently, when parse_options() produces a help message it always emits > a blank line after the usage text to separate it from the options text. > If the option spec does not define any switches, or only defines hi

[PATCH 3/3] parse-options: only insert newline in help text if needed

Currently, when parse_options() produces a help message it always emits a blank line after the usage text to separate it from the options text. If the option spec does not define any switches, or only defines hidden switches that will not be displayed, then the help text will end up with two

[PATCH 13/13] pack-objects: add filtering help text

From: Jeff Hostetler <jeffh...@microsoft.com> Add help text for new object filtering options to pack-objects documentation. Signed-off-by: Jeff Hostetler <jeffh...@microsoft.com> --- Documentation/git-pack-objects.txt | 17 + 1 file changed, 17 insertions(+)

[PATCH 10/13] rev-list: add filtering help text

From: Jeff Hostetler Signed-off-by: Jeff Hostetler --- Documentation/git-rev-list.txt | 9 - Documentation/rev-list-options.txt | 32 2 files changed, 40 insertions(+), 1 deletion(-) diff --git

[PATCH 2/4] rev-parse parseopt: do not search help text for flag chars

When searching for flag characters in the option spec, we should ensure the search stays within the bounds of the option spec and does not enter the help text portion of the spec. So when we find the boundary white space marking the start of the help text, let's mark it with a nul character

[PATCH 3/4] rev-parse parseopt: interpret any whitespace as start of help text

Currently, rev-parse only interprets a space ' ' character as the delimiter between the option spec and the help text. So if a tab character is placed between the option spec and the help text, it will be interpreted as part of the long option name or as part of the arg hint

[PATCH] help: change a message to be more precise

When the user tries to use '--help' option on an aliased command information about the alias is printed as sshown below, $ git co --help `git co' is aliased to `checkout' This doesn't seem correct as the user has aliased only 'co' and not 'git co'. This might even be incorrect in cases

I NEED YOUR HELP

Greetings, I am Miss elizabeth 22 years old i have every important things to discus with you. Please respond with your most secure email address to enable me give you the brief details of proposer, please write me on this email elizabethcot...@barid.com Looking forward for your positive

[PATCH 13/34] help: release strbuf on error return in exec_man_konqueror()

Signed-off-by: Rene Scharfe --- builtin/help.c | 1 + 1 file changed, 1 insertion(+) diff --git a/builtin/help.c b/builtin/help.c index 334a8494ab..991a8bb16c 100644 --- a/builtin/help.c +++ b/builtin/help.c @@ -137,21 +137,22 @@ static void exec_woman_emacs(const char *path,

[PATCH 15/34] help: release strbuf on error return in exec_woman_emacs()

Signed-off-by: Rene Scharfe --- builtin/help.c | 1 + 1 file changed, 1 insertion(+) diff --git a/builtin/help.c b/builtin/help.c index 12fb48933e..b3f60a8f30 100644 --- a/builtin/help.c +++ b/builtin/help.c @@ -123,14 +123,15 @@ static int check_emacsclient_version(void) static

[PATCH 14/34] help: release strbuf on error return in exec_man_man()

Signed-off-by: Rene Scharfe --- builtin/help.c | 1 + 1 file changed, 1 insertion(+) diff --git a/builtin/help.c b/builtin/help.c index 991a8bb16c..12fb48933e 100644 --- a/builtin/help.c +++ b/builtin/help.c @@ -167,9 +167,10 @@ static void exec_man_man(const char *path, const

Re: Remove help advice text from git editors for interactive rebase and reword

advices configurable via the 'advice.commitMsg' > config variable. It may not be a bad idea, but the code after the patch does look ugly with too deep indentation levels. Can some refactoring help, I wonder? Is that advice.commitMsg? It looks more like commitEditor advice to me but it may be just me.

Re: Remove help advice text from git editors for interactive rebase and reword

> So I actually would be OK with having an advice.* option to squelch > rebase and/or commit instructions. But only if users decide they would > never like to see that text. So yes, your tool could piggy-back on that > config option, but it would be a slight abuse of the intent. I don't mind the

Re: Remove help advice text from git editors for interactive rebase and reword

On Mon, Jul 24, 2017 at 01:26:09AM +0300, Kirill Likhodedov wrote: > > Not at all interested, as that would mean your tool will tell its > > users to set such a configuration variable and their interactive use > > of Git outside your tool will behave differently from other people > > who use

Re: Remove help advice text from git editors for interactive rebase and reword

> On 24 Jul 2017, at 01:09 , Junio C Hamano wrote: > > Who is running "git commit --amend" and "git rebase -i" in the > workflow of a user of your tool? Is it the end user who types these > commands to the shell command prompt, or does your tool formulate > the command line

Re: Remove help advice text from git editors for interactive rebase and reword

Kirill Likhodedov writes: > My motivation is the following: I'm improving the Git client > inside of IntelliJ IDEA IDE and I would like to provide only the > plain commit message text to the user (any hints can be shown > separately, not inside the editor). Who

Re: Remove help advice text from git editors for interactive rebase and reword

eractive rebase is implemented in git-rebase--interactive.sh which always makes a call to append_todo_help to append the help text to the todo list of commits. > and the one which appears at the bottom of the commit editor (which > appears on rewording a commit or squashing commits)? This one too

Remove help advice text from git editors for interactive rebase and reword

the plain commit message text to the user (any hints can be shown separately, not inside the editor). I know I can load the original commit message myself (but I prefer not to make extra calls when possible); and I can parse and strip out the help pages (but it is not very reliable since the text may

[PATCH v2 09/19] rev-list: add filtering help text

From: Jeff Hostetler Signed-off-by: Jeff Hostetler --- Documentation/git-rev-list.txt | 7 ++- Documentation/rev-list-options.txt | 26 ++ 2 files changed, 32 insertions(+), 1 deletion(-) diff --git

[PATCH v2 12/19] pack-objects: add filtering help text

From: Jeff Hostetler <jeffh...@microsoft.com> Update pack-objects help text to describe object filtering. Signed-off-by: Jeff Hostetler <jeffh...@microsoft.com> --- Documentation/git-pack-objects.txt | 14 ++ 1 file changed, 14 insertions(+) diff --git a/Documentat

Re: git config --help not functional on bad config

On Tue, Jul 11, 2017 at 12:13:59PM -0700, Stefan Beller wrote: > > There are other die calls hidden deeper. For instance: > > > > $ git -c core.ignorecase=foo help config > > fatal: bad numeric config value 'foo' for 'core.ignorecase': invalid unit > > > >

Re: git config --help not functional on bad config

gt; > - return git_default_config(var, value, cb); >> > + return 0; >> >> Instead of ignoring any default config, we could do >> >> git_default_config(var, value, cb); >> /* ignore broken config, we may be the help call for conf

Re: git config --help not functional on bad config

gnoring any default config, we could do > > git_default_config(var, value, cb); > /* ignore broken config, we may be the help call for config */ > return 0; > > I looked through git_default_config which seems to only die > with useful error messages for compressio

Re: git config --help not functional on bad config

On Tue, Jul 11, 2017 at 10:53 AM, Jeff King <p...@peff.net> wrote: > On Tue, Jul 11, 2017 at 03:49:21PM +0100, Peter Krefting wrote: > >> That's fine. However, when trying to look for help, it is not that useful: >> >> $ git config --help >> error: malfor

Re: git config --help not functional on bad config

On Tue, Jul 11, 2017 at 03:49:21PM +0100, Peter Krefting wrote: > That's fine. However, when trying to look for help, it is not that useful: > > $ git config --help > error: malformed value for branch.autosetuprebase > fatal: bad config variable 'branch.autosetuprebase

git config --help not functional on bad config

trying to look for help, it is not that useful: $ git config --help error: malformed value for branch.autosetuprebase fatal: bad config variable 'branch.autosetuprebase' in file '.git/config' at line 24 Perhaps it should allow "--help" to go through even if the configurat

Re: Help needed for solving a few issues with building git

anything I did, wrong? > Ok, at last I was able to build git with https support using 'curl' built from it's source. Anyways, thanks for the help, folks. > >  This is probably because you are trying to run without installing? > > Nope. I'm *installing* git not

Re: Help needed for solving a few issues with building git

at bin-wrappers/ directory at the > top-level of your build tree (that is how our tests can run on an > otherwise virgin box with no Git installed). > On Mon, 2017-07-03 at 13:11 -0700, Junio C Hamano wrote: > Junio C Hamano <gits...@pobox.com> writes: > > $ make N

Re: Help needed for solving a few issues with building git

uld I be missing? > > There is > > ifndef NO_GETTEXT > all:: $(MOFILES) > endif > > which attempts to avoid generating *.mo files, but that does not > seem to be working. The above comes from one of the Tcl things (probably gitk-git) For now $ make NO_GETTEXT=1 N

Re: Help needed for solving a few issues with building git

Kaartic Sivaraam writes: > Hello all, > > Building without localization support > > I tried to build git from source without localization support by adding > the following line to the Makefile, > > NO_GETTEXT=1 > > It

Re: Help needed for solving a few issues with building git

On 2017-07-03 15:18, Kaartic Sivaraam wrote: > Hello all, > > Building without localization support > > I tried to build git from source without localization support by adding > the following line to the Makefile, > > NO_GETTEXT=1 > May be make

Help needed for solving a few issues with building git

Hello all, Building without localization support I tried to build git from source without localization support by adding the following line to the Makefile, NO_GETTEXT=1 It doesn't seem to be working for reasons I'm unable to find. I used the following

I need you help pls

HELP ME PLEASE My name is Miss Victoria Jenny looking for a trustworthy, sincere and honest someone like you who can help me in this time of needs. My father is Rufus Okana, during the civil and political crisis in our country, my parents together with my three sisters was poisoned by heartless

Re: [PATCH 1/1] ls-remote: remove "-h" from help text

Hi Jonathan, > > This regression was fixed in 91a640ffb6d9 ("ls-remote: a lone "-h" is > > [...] > > Without this patch, I'm able to run > > git ls-remote -h . > > This patch removes that support. Intended? *hihi* okay it was to counter-intuitive for me. "91a640ffb6d" talks about this

Re: [PATCH 1/1] ls-remote: remove "-h" from help text

Hi, Silvio Fricke wrote: > This regression was fixed in 91a640ffb6d9 ("ls-remote: a lone "-h" is > asking for help") and the wrong help text was introduced in ba5f28bf79ea > ("ls-remote: use parse-options api"). > This patch removes the "-h"

[PATCH 0/1] fix ls-remote help message

Hi, a small patch about a wrong help text. Please include when okay. Best Regards, Silvio Silvio Fricke (1): ls-remote: remove "-h" from help text builtin/ls-remote.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 2.13.2

[PATCH 1/1] ls-remote: remove "-h" from help text

This regression was fixed in 91a640ffb6d9 ("ls-remote: a lone "-h" is asking for help") and the wrong help text was introduced in ba5f28bf79ea ("ls-remote: use parse-options api"). This patch removes the "-h" on the help text. Signed-off-by: Silvio Fricke &

Re: Using '--help' for aliases

On Thu, Jun 22, 2017 at 12:11:29AM +0530, Kaartic Sivaraam wrote: > I am yet another user of 'git alias' (who wouldn't ?). It has become so > natural to me to use the aliased version that at some point of time I > tried the following, > > > $ git co --help > > `git co'

Re: Using '--help' for aliases

You could also just make the alias a bash function that does git help checkout when you pass the --help flag to the alias.

Re: [PATCHv2 (resend)] Tweak help auto-correct phrasing.

Marc Branchaud writes: > When auto-correct is enabled, an invalid git command prints a warning and > a continuation message, which differs depending on whether or not > help.autoCorrect is positive or negative. > > With help.autoCorrect = 15: > >WARNING: You called a

Re: Using '--help' for aliases

ion is whether it is more important to tell the user that it's > an > alias (and which options the alias is using!), Now, that's something I didn't think of. Does seem to quite an issue as aliases accept argument this. I seem to be getting the idea of '--help' just now. All these d

Re: Using '--help' for aliases

On Thu, Jun 22, 2017 at 12:11:29AM +0530, Kaartic Sivaraam wrote: > I am yet another user of 'git alias' (who wouldn't ?). It has become so > natural to me to use the aliased version that at some point of time I > tried the following, > > > $ git co --help > > `git co'

Using '--help' for aliases

Hello all, I am yet another user of 'git alias' (who wouldn't ?). It has become so natural to me to use the aliased version that at some point of time I tried the following, > $ git co --help > `git co' is aliased to `checkout' That made me wonder. Git is able to inform the user th

[PATCHv2 (resend)] Tweak help auto-correct phrasing.

When auto-correct is enabled, an invalid git command prints a warning and a continuation message, which differs depending on whether or not help.autoCorrect is positive or negative. With help.autoCorrect = 15: WARNING: You called a Git command named 'lgo', which does not exist. Continuing

git revert --continue refuses to, help!

Hi! What do I do next, to finish reverting multiple commits? I'd use '--skip' in 'git rebase', but 'revert' doesn't have one? [skeleton (tmp|REVERTING)]$ git revert --continue On branch tmp You are currently reverting commit d8a30d3. nothing to commit, working tree clean [skeleton

Re: [PATCHv2] Tweak help auto-correct phrasing.

On Tue, 2016-12-20 at 09:02 -0500, Marc Branchaud wrote: > When auto-correct is enabled, an invalid git command prints a warning > and > a continuation message, which differs depending on whether or not > help.autoCorrect is positive or negative. > > With help.autoCorrect = 15: > >    WARNING:

Re: [PATCHv2] Tweak help auto-correct phrasing.

On 2017-06-20 02:04 PM, Kaartic Sivaraam wrote: On Tue, 2016-12-20 at 09:02 -0500, Marc Branchaud wrote: When auto-correct is enabled, an invalid git command prints a warning and a continuation message, which differs depending on whether or not help.autoCorrect is positive or negative. With

Re: [PATCHv2] Tweak help auto-correct phrasing.

On Tue, 2016-12-20 at 09:02 -0500, Marc Branchaud wrote: > When auto-correct is enabled, an invalid git command prints a warning > and > a continuation message, which differs depending on whether or not > help.autoCorrect is positive or negative. > > With help.autoCorrect = 15: > >    WARNING:

[PATCH v4 3/6] help: use early config when autocorrecting aliases

Git has this feature which suggests similar commands (including aliases) in case the user specified an unknown command. This feature currently relies on a side effect of the way we expand aliases right now: when a command is not a builtin, we use the regular config machinery (meaning: discovering

[PATCH v3 3/6] help: use early config when autocorrecting aliases

Git has this feature which suggests similar commands (including aliases) in case the user specified an unknown command. This feature currently relies on a side effect of the way we expand aliases right now: when a command is not a builtin, we use the regular config machinery (meaning: discovering

PLEASE I NEED YOUR HELP

on 28th July, 2011 and after two days later my mother with my two brothers was killed one early morning by the rebels as result of civil war that going on in my country Libya. I am now writing to seek for your assistance from Guinea Conakry where I managed to escape nearby country through the help

Re: [PATCH v2 3/8] help: use early config when autocorrecting aliases

On Thu, Jun 08, 2017 at 09:53:38PM +0200, Johannes Schindelin wrote: > Git has this feature which suggests similar commands (including aliases) > in case the user specified an unknown command. > > This feature currently relies on a side effect of the way we expand > aliases right now: when a

Re: [PATCH 3/9] help: use early config when autocorrecting aliases

Johannes Schindelin writes: > This is slightly less performant than the previous way, as the early > config is used *twice*: once to see whether the command refers to an > alias, and then to see what aliases are most similar. However, this is > hardly a

[PATCH v2 3/8] help: use early config when autocorrecting aliases

Git has this feature which suggests similar commands (including aliases) in case the user specified an unknown command. This feature currently relies on a side effect of the way we expand aliases right now: when a command is not a builtin, we use the regular config machinery (meaning: discovering

Re: [PATCH 3/9] help: use early config when autocorrecting aliases

Hi Brandon, On Wed, 7 Jun 2017, Brandon Williams wrote: > On 06/07, Johannes Schindelin wrote: > > Git has this feature where suggests similar commands (including aliases) > > nit: s/where/which/ > > > in case that the user specified an unknown command. > > s/that// Oh my. Thank you so much!

Re: [PATCH 3/9] help: use early config when autocorrecting aliases

On 06/07, Johannes Schindelin wrote: > Git has this feature where suggests similar commands (including aliases) nit: s/where/which/ > in case that the user specified an unknown command. s/that// > > This feature currently relies on a side effect of the way we expand > aliases right now: when

[PATCH 3/9] help: use early config when autocorrecting aliases

Git has this feature where suggests similar commands (including aliases) in case that the user specified an unknown command. This feature currently relies on a side effect of the way we expand aliases right now: when a command is not a builtin, we use the regular config machinery (meaning:

Re: [BUG] Help > About Git Gui = crash

Hi, On Tue, 6 Jun 2017, Konstantin Podsvirov wrote: > 06.06.2017, 21:25, "Stefan Beller" <sbel...@google.com>: > > On Tue, Jun 6, 2017 at 10:34 AM, Konstantin Podsvirov > > <konstan...@podsvirov.pro> wrote: > >>  Reproduction: > >>  - Start

Re: [BUG] Help > About Git Gui = crash

06.06.2017, 21:25, "Stefan Beller" <sbel...@google.com>: > On Tue, Jun 6, 2017 at 10:34 AM, Konstantin Podsvirov > <konstan...@podsvirov.pro> wrote: >>  Reproduction: >>  - Start git gui >>  - Go to menu panel: Help > About Git Gui &g

Re: [BUG] Help > About Git Gui = crash

On Tue, Jun 6, 2017 at 10:34 AM, Konstantin Podsvirov <konstan...@podsvirov.pro> wrote: > Reproduction: > - Start git gui > - Go to menu panel: Help > About Git Gui > > Output: > error: git-gui died of signal 11 > > Environment: > Debian 8 jessie amd6

[BUG] Help > About Git Gui = crash

Reproduction: - Start git gui - Go to menu panel: Help > About Git Gui Output: error: git-gui died of signal 11 Environment: Debian 8 jessie amd64 KDE -- Regards, Konstantin Podsvirov

[PATCH v4 13/25] setup_bare_git_dir(): help static analysis

Coverity reported a memory leak in this function. However, it can only be called once, as setup_git_directory() changes global state and hence is not reentrant. Mark the variable as static to indicate that this is a singleton. Signed-off-by: Johannes Schindelin ---

Re: Reference help

On Tue, May 2, 2017 at 9:33 PM, Desjardin, Donald wrote: > Sorry if this is not the place for this. > > I'm looking for any reference to potential problems when updating a git > client (say from 1.7.N to 1.8.N) with old workspaces. > > The scenario is this: >

Reference help

Sorry if this is not the place for this. I'm looking for any reference to potential problems when updating a git client (say from 1.7.N to 1.8.N) with old workspaces. The scenario is this: Lots of developers use a single machine for work They have lots of workspaces created

[PATCH v3 13/25] setup_bare_git_dir(): help static analysis

Coverity reported a memory leak in this function. However, it can only be called once, as setup_git_directory() changes global state and hence is not reentrant. Mark the variable as static to indicate that this is a singleton. Signed-off-by: Johannes Schindelin ---

Re: [PATCH v2 14/25] setup_discovered_git_dir(): help static analysis

Hi Junio, On Mon, 1 May 2017, Junio C Hamano wrote: > Johannes Schindelin writes: > > > Coverity reported a memory leak in this function. However, it can only > > be called once, as setup_git_directory() changes global state and hence > > is not reentrant. > > > >

Re: [PATCH v2 14/25] setup_discovered_git_dir(): help static analysis

Johannes Schindelin writes: > Coverity reported a memory leak in this function. However, it can only > be called once, as setup_git_directory() changes global state and hence > is not reentrant. > > Mark the variable as static to indicate that this is a singleton. > >

[PATCH v2 14/25] setup_discovered_git_dir(): help static analysis

Coverity reported a memory leak in this function. However, it can only be called once, as setup_git_directory() changes global state and hence is not reentrant. Mark the variable as static to indicate that this is a singleton. Signed-off-by: Johannes Schindelin ---

[PATCH v2 13/25] setup_bare_git_dir(): help static analysis

Coverity reported a memory leak in this function. However, it can only be called once, as setup_git_directory() changes global state and hence is not reentrant. Mark the variable as static to indicate that this is a singleton. Signed-off-by: Johannes Schindelin ---

Re: [Suggestion] Alternative way for displaying help menu of patch flow

patch does for help), and you'd get: @@ -1 +1 @@ -old +new Stage this hunk [y,n,q,a,d,/,e,?]? j No next hunk Stage this hunk [y,n,q,a,d,/,e,?]? at which point you could "r" to redisplay it if you wanted to. This seems good too. But, I guess, the help menu would probably hid

<    1   2   3   4   5   6   7   8   9   10   >