Re: Git Error Message

On Mon, Jun 05, 2017 at 02:54:55PM +0100, Philip Oakley wrote: > > > I have installed the Git software and upon trying to update a > > > repository by the "open recent repository" link and am unable to > > > access the menu-or anything-from there. Instead a window pops up with > > > the

Re: Git Error Message

From: "Konstantin Khomoutov" On Sat, Jun 03, 2017 at 01:13:05AM -0700, christienne shultz wrote: I have installed the Git software and upon trying to update a repository by the "open recent repository" link and am unable to access the menu-or anything-from there.

Re: Git Error Message

On Sat, Jun 03, 2017 at 01:13:05AM -0700, christienne shultz wrote: > I have installed the Git software and upon trying to update a > repository by the "open recent repository" link and am unable to > access the menu-or anything-from there. Instead a window pops up with > the following error

Git Error Message

Hello, I have installed the Git software and upon trying to update a repository by the "open recent repository" link and am unable to access the menu-or anything-from there. Instead a window pops up with the following error message: "\usage C:\Program Files\Git\mingw64/libexec/git-core\git-GUI[

Re: git error

Hi Ada, On Fri, 5 May 2017, ada wrote: > I used the command below,there's an error,please help me to solve it ! > Thank you ~ > git push I am sorry to hear that you encountered a problem using Git. Having said that, this description does not allow anybody to help you, as not even the error

Re: git error

On Fri, May 05, 2017 at 10:52:13AM +0800, ada wrote: > hi, > > I used the command below,there's an error,please help me to solve it ! > Thank you ~ > git push > > > Best Regards~ > ada Wang > Hello Ada, In order for people to be able to help you, you should provide more details about your

git error

hi, I used the command below,there's an error,please help me to solve it ! Thank you ~ git push Best Regards~ ada Wang

[PATCH v11 11/14] convert: make apply_filter() adhere to standard Git error handling

From: Lars Schneider apply_filter() returns a boolean that tells the caller if it "did convert or did not convert". The variable `ret` was used throughout the function to track errors whereas `1` denoted success and `0` failure. This is unusual for the Git source where

[PATCH v10 11/14] convert: make apply_filter() adhere to standard Git error handling

From: Lars Schneider apply_filter() returns a boolean that tells the caller if it "did convert or did not convert". The variable `ret` was used throughout the function to track errors whereas `1` denoted success and `0` failure. This is unusual for the Git source where

[PATCH v9 11/14] convert: make apply_filter() adhere to standard Git error handling

From: Lars Schneider apply_filter() returns a boolean that tells the caller if it "did convert or did not convert". The variable `ret` was used throughout the function to track errors whereas `1` denoted success and `0` failure. This is unusual for the Git source where

Re: [PATCH v8 10/11] convert: make apply_filter() adhere to standard Git error handling

W dniu 20.09.2016 o 21:02, larsxschnei...@gmail.com pisze: > From: Lars Schneider > > apply_filter() returns a boolean that tells the caller if it > "did convert or did not convert". The variable `ret` was used throughout > the function to track errors whereas `1`

[PATCH v8 10/11] convert: make apply_filter() adhere to standard Git error handling

From: Lars Schneider apply_filter() returns a boolean that tells the caller if it "did convert or did not convert". The variable `ret` was used throughout the function to track errors whereas `1` denoted success and `0` failure. This is unusual for the Git source where

[PATCH v7 09/10] convert: make apply_filter() adhere to standard Git error handling

From: Lars Schneider apply_filter() returns a boolean that tells the caller if it "did convert or did not convert". The variable `ret` was used throughout the function to track errors whereas `1` denoted success and `0` failure. This is unusual for the Git source where

[PATCH v6 11/13] convert: make apply_filter() adhere to standard Git error handling

From: Lars Schneider apply_filter() returns a boolean that tells the caller if it "did convert or did not convert". The variable `ret` was used throughout the function to track errors whereas `1` denoted success and `0` failure. This is unusual for the Git source where

[PATCH v5 13/15] convert: make apply_filter() adhere to standard Git error handling

From: Lars Schneider apply_filter() returns a boolean that tells the caller if it "did convert or did not convert". The variable `ret` was used throughout the function to track errors wheras `1` denoted success and `0` failure. This is unusual for the Git source where

Re: git error in tag ...: unterminated header

Hi Junio, On 2015-06-26 19:37, Junio C Hamano wrote: Jeff King p...@peff.net writes: On Fri, Jun 26, 2015 at 10:06:20AM +0200, Johannes Schindelin wrote: I understood what you were saying, but it still appears too fragile to me to mix functions that assume NUL-terminated strings with an

Re: git error in tag ...: unterminated header

Johannes Schindelin johannes.schinde...@gmx.de writes: On 2015-06-26 19:37, Junio C Hamano wrote: Jeff King p...@peff.net writes: On Fri, Jun 26, 2015 at 10:06:20AM +0200, Johannes Schindelin wrote: I understood what you were saying, but it still appears too fragile to me to mix functions

Re: git error in tag ...: unterminated header

Hi Junio, On 2015-06-26 00:29, Junio C Hamano wrote: Junio C Hamano gits...@pobox.com writes: Johannes Schindelin johannes.schinde...@gmx.de writes: ... If the buffer does *not* contain an empty line, the fsck code runs the danger of looking beyond the allocated memory because it uses

Re: git error in tag ...: unterminated header

On Fri, Jun 26, 2015 at 10:06:20AM +0200, Johannes Schindelin wrote: I understood what you were saying, but it still appears too fragile to me to mix functions that assume NUL-terminated strings with an ad-hoc counted string check. Yeah, I agree. It is not that you cannot make it safe, but

Re: git error in tag ...: unterminated header

Jeff King p...@peff.net writes: On Fri, Jun 26, 2015 at 10:06:20AM +0200, Johannes Schindelin wrote: I understood what you were saying, but it still appears too fragile to me to mix functions that assume NUL-terminated strings with an ad-hoc counted string check. Yeah, I agree. It is not

Re: git error in tag ...: unterminated header

Dear Junio, thanks for the fast replies. In message xmqqegkzzoaz@gitster.dls.corp.google.com you wrote: Question is: how can we fix that? It could be that 4d0d8975 is buggy and barking at a non breakage. If there is no message in the tag, i.e. -- 8 -- object

Re: git error in tag ...: unterminated header

Wolfgang Denk w...@denx.de writes: Hm... it seems I cannot even easily delte these tags: - git tag -d LABEL_2006_03_12_0025 Deleted tag 'LABEL_2006_03_12_0025' (was eb394f5) - git fsck --full Checking object directories: 100% (256/256), done. Checking object directories: 100% (256/256),

Re: git error in tag ...: unterminated header

Wolfgang Denk w...@denx.de writes: Dear Junio, thanks for the fast replies. In message xmqqegkzzoaz@gitster.dls.corp.google.com you wrote: Question is: how can we fix that? It could be that 4d0d8975 is buggy and barking at a non breakage. If there is no message in the tag, i.e.

Re: git error in tag ...: unterminated header

Hi Junio Wolfgang, On 2015-06-25 22:24, Junio C Hamano wrote: Wolfgang Denk w...@denx.de writes: In message xmqqegkzzoaz@gitster.dls.corp.google.com you wrote: Question is: how can we fix that? It could be that 4d0d8975 is buggy and barking at a non breakage. Well, I would like to

Re: git error in tag ...: unterminated header

Johannes Schindelin johannes.schinde...@gmx.de writes: Hi Junio Wolfgang, On 2015-06-25 22:24, Junio C Hamano wrote: Wolfgang Denk w...@denx.de writes: In message xmqqegkzzoaz@gitster.dls.corp.google.com you wrote: Question is: how can we fix that? It could be that 4d0d8975 is

git error in tag ...: unterminated header

Hi all, it turns out that recent versions of git (i. e. git version 2.2.0 or later, resp. anything which includes commit 4d0d8975 Make sure fsck_commit_buffer() does not run out of the buffer) throws errors on our git repository git://git.denx.de/u-boot: - git fsck --full Checking object

Re: git error in tag ...: unterminated header

Wolfgang Denk w...@denx.de writes: Apparently for some reason the tags LABEL_2006_03_12_0025, LABEL_2006_04_18_1106, and LABEL_2006_05_19_1133 are missing newlines, which was undetected so far, but now is raised as an error. Question is: how can we fix that? Is there a tool to auto-repair

Re: git error in tag ...: unterminated header

Wolfgang Denk w...@denx.de writes: it turns out that recent versions of git (i. e. git version 2.2.0 or later, resp. anything which includes commit 4d0d8975 Make sure fsck_commit_buffer() does not run out of the buffer) throws errors on our git repository git://git.denx.de/u-boot: - git

Re: git error in tag ...: unterminated header

Junio C Hamano gits...@pobox.com writes: Johannes Schindelin johannes.schinde...@gmx.de writes: ... If the buffer does *not* contain an empty line, the fsck code runs the danger of looking beyond the allocated memory because it uses functions that assume NUL-terminated strings, while the

assistance with git error

Could someone provide me some assistance with troubleshooting the following: remote: Counting objects: 31654, done. error: pack-objects died of signal 99568/19585) error: git upload-pack: git-pack-objects died with error. fatal: git upload-pack: aborting due to possible repository corruption

Re: assistance with git error

On Tue, Feb 24, 2015 at 08:40:56PM +, Tom wrote: Could someone provide me some assistance with troubleshooting the following: remote: Counting objects: 31654, done. error: pack-objects died of signal 99568/19585) The output is smushed here due to the use of \r for the progress

Re: assistance with git error

On Tue, Feb 24, 2015 at 04:49:00PM -0500, Thomas Moretto wrote: i also have a question concerning large files. Sure, but let's take it back on-list. Then other people can help answer, and later users can benefit from seeing the answers. i ran a check and it said there was a schema.sql file

RE: GIt error

Sent: Monday, June 17, 2013 6:51 PM To: 'git@vger.kernel.org' Subject: RE: GIt error Hi, 1.Iam getting error attached when cloning of repository is done: 2.Also, when file is tried to be added,it gives error below: $ git add * fatal: unable to stat 'src/development_architecture

Re: GIt error

On Mon, Jun 17, 2013 at 01:28:30PM +, justin.sathyanat...@accenture.com wrote: 1.Iam getting error attached when cloning of repository is done: What error? 2.Also, when file is tried to be added,it gives error below: $ git add * fatal: unable to stat

Re: GIt error

On Mon, 17 Jun 2013 13:28:30 + justin.sathyanat...@accenture.com wrote: For Below issue , O/S is Windows7. [...] 1.Iam getting error attached when cloning of repository is done: What error? 2.Also, when file is tried to be added,it gives error below: $ git add * fatal: unable to stat

Re: GIt error

On Mon, 17 Jun 2013 17:47:07 +0400 Konstantin Khomoutov kostix+...@007spb.ru wrote: For Below issue , O/S is Windows7. 1.Iam getting error attached when cloning of repository is done: What error? Okay, the Microsoft Word document with two screenshots has been scrubbed by the list software